-
Notifications
You must be signed in to change notification settings - Fork 335
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]: enable reduce_stop_for_best for iterator #1830
Comments
MrPresent-Han
added a commit
to MrPresent-Han/pymilvus
that referenced
this issue
Dec 27, 2023
Signed-off-by: MrPresent-Han <[email protected]>
MrPresent-Han
added a commit
to MrPresent-Han/pymilvus
that referenced
this issue
Dec 27, 2023
Signed-off-by: MrPresent-Han <[email protected]>
MrPresent-Han
added a commit
to MrPresent-Han/pymilvus
that referenced
this issue
Dec 27, 2023
Signed-off-by: MrPresent-Han <[email protected]>
MrPresent-Han
added a commit
to MrPresent-Han/pymilvus
that referenced
this issue
Dec 27, 2023
Signed-off-by: MrPresent-Han <[email protected]>
This was referenced Dec 27, 2023
sre-ci-robot
pushed a commit
that referenced
this issue
Dec 28, 2023
Signed-off-by: MrPresent-Han <[email protected]>
sre-ci-robot
pushed a commit
that referenced
this issue
Dec 28, 2023
Signed-off-by: MrPresent-Han <[email protected]>
close for done |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
Describe the bug
In the past, without using reduce_stop_for_best, iterator may get incorrect results from query node due to duplicated ids, which result in iteration ending ahead
Expected Behavior
No response
Steps/Code To Reproduce behavior
No response
Environment details
Anything else?
No response
The text was updated successfully, but these errors were encountered: