-
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]: Empty TopK query result with expr while non-empty result without expr #37683
Comments
/assign @xiaocai2333 |
When I changed from "query" to "filter" in expression, the result is normal and non-empty. Quite strange. is there any difference between the two words? |
you mean changing the key word from "expr" to "filter" in the search() request? |
@liuxiang-github |
also we would recommend to use 2.4.14 on the test. We don't find similar issues so if you still hit that you will need to check you test script. We would definitely love to help. |
It might be related to the index you are using. When scalar filtering is applied, it may disrupt the connectivity of the HNSW index graph, leading to degraded search performance. In version 2.4, we optimized this behavior to ensure that data can be retrieved. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Is there an existing issue for this?
Environment
Current Behavior
Hi team,
When we execute the topk query with expr, the result is empty.
But if we remove expr, the result is non-empty.
Record number of entire collection: 5166
Record number that matches the expr: 833
Could you help check the root cause?
table schema:
Expected Behavior
For the query filter which attu returned non-empty result, the topk query should also return non-empty result.
Steps To Reproduce
No response
Milvus Log
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: