Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Pymilvus erroneously presumes the primary key to be named "id" when deal with SearchResults #2558

Open
1 task done
czs007 opened this issue Jan 13, 2025 · 1 comment
Assignees
Labels
kind/bug Something isn't working
Milestone

Comments

@czs007
Copy link
Contributor

czs007 commented Jan 13, 2025

Is there an existing issue for this?

  • I have searched the existing issues

Describe the bug

Pymilvus erroneously presumes the primary key to be named "id" when deal with SearchResults

Expected Behavior

Determine the name of the primary field based on the primary_field_name in the returned results.

Steps/Code To Reproduce behavior

No response

Environment details

- Hardware/Softward conditions (OS, CPU, GPU, Memory):
- Method of installation (Docker, or from source):
- Milvus version (v0.3.1, or v0.4.0):
- Milvus configuration (Settings you made in `server_config.yaml`):

Anything else?

No response

@XuanYang-cn
Copy link
Contributor

/assign @czs007

sre-ci-robot pushed a commit that referenced this issue Jan 13, 2025
sre-ci-robot pushed a commit that referenced this issue Jan 13, 2025
sre-ci-robot pushed a commit that referenced this issue Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants