-
Notifications
You must be signed in to change notification settings - Fork 3k
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]: [int8_vector] The int8_vector is not shown in the results when specifying the int8_vector field as output_fields for query #39847
Labels
kind/bug
Issues or changes related a bug
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Milestone
Comments
/assign @cydrain |
And the default result for query is different between float_vector and int8_vector too: float_vector: (vector is included)
int8_vector (vector is not included)
|
@binbinlv
|
Ok, will verify it when the fix pr is merged. |
sre-ci-robot
pushed a commit
to milvus-io/pymilvus
that referenced
this issue
Feb 14, 2025
issue: milvus-io/milvus#39847 Signed-off-by: CaiYudong <[email protected]>
@binbinlv fix merged |
Verified and fixed: pymilvus: 2.6.0rc72 results:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
kind/bug
Issues or changes related a bug
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Is there an existing issue for this?
Environment
Current Behavior
The int8_vector is not shown in the results when specifying the int8_vector field as output_fields for query
Expected Behavior
The int8_vector is shown in the results when specifying the int8_vector field as output_fields for query
just like float_vector:
Steps To Reproduce
Milvus Log
https://grafana-4am.zilliz.cc/explore?orgId=1&panes=%7B%22Fjq%22:%7B%22datasource%22:%22vhI6Vw67k%22,%22queries%22:%5B%7B%22refId%22:%22A%22,%22expr%22:%22%7Bcluster%3D%5C%22devops%5C%22,namespace%3D%5C%22chaos-testing%5C%22,pod%3D~%5C%22master-latest-lpbqj.%2A%5C%22%7D%22,%22datasource%22:%7B%22type%22:%22loki%22,%22uid%22:%22vhI6Vw67k%22%7D%7D%5D,%22range%22:%7B%22from%22:%22now-1h%22,%22to%22:%22now%22%7D%7D%7D&schemaVersion=1
Anything else?
collection name: customized_setup_1
timeline: about 2025-02-13 14:38
The text was updated successfully, but these errors were encountered: