-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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]: Filtering by partition key fails to return results for bulk imported data #33237
Comments
/assign @zhuwenxing |
/assign @bigsheeper |
Yes, this issue can be reproduced.
only op |
working on it |
Before executing the import, partition IDs should be reordered according to partition names. Otherwise, the data might be hashed to the wrong partition during import. This PR corrects this error. issue: #33237 --------- Signed-off-by: bigsheeper <yihao.dai@zilliz.com>
/assign @zhuwenxing |
see #33237 Signed-off-by: zhuwenxing <wenxing.zhu@zilliz.com>
@zhuwenxing Thank you for the quick resolution! |
Is there an existing issue for this?
Environment
Current Behavior
I import data using the bulk import feature with a parquet file containing the following fields:
item_id
(primary key)partition_id
(partition key)embedding
(float vector)I can successfully query and filter by
item_id
.However, when I attempt to filter by
partition_id
(partition key) with an existing value, the result set is empty.This behavior is observed using both the Python SDK and the Attu UI.
This behavior cannot be reproduced when I insert the same data using the Python SDK.
Expected Behavior
When importing data using the bulk import feature and filtering by the partition key with an existing value, the result set should contain all entries for the queried partition key.
Steps To Reproduce
Milvus Log
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: