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]: Range Filter Bug #33383

Closed
1 task done
JackTan25 opened this issue May 25, 2024 · 5 comments
Closed
1 task done

[Bug]: Range Filter Bug #33383

JackTan25 opened this issue May 25, 2024 · 5 comments
Assignees
Labels
kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@JackTan25
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version: 2.4.3
- Deployment mode(standalone or cluster): standalone
- MQ type(rocksmq, pulsar or kafka): kafka    
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS): 
- CPU/Memory: 
- GPU: 
- Others:

Current Behavior

Get wrong result for range query.

Expected Behavior

Get null result.

Steps To Reproduce

use my script

Milvus Log

No response

Anything else?

No response

@JackTan25 JackTan25 added kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels May 25, 2024
@JackTan25
Copy link
Author

JackTan25 commented May 25, 2024

small_data-2.zip
cc @czs007 @yanliang567 The range search get wrong result.

$ cd small_data
## we can get all data distances to the query point.
$ python3.11 ground_truth.py 
## the radius is 100, should get non result, but get topk results.
$ python3.11 milvus_small_multi_vector.py 

It seems the radius filter doesn't take effect. Please help me, I'm in hurry.

@xiaofan-luan
Copy link
Collaborator

/assign @liliu-z could you help on investigating this?

@chasingegg
Copy link
Contributor

This is not a bug, should be a mis-use of pymilvus api, @JackTan25 help check this.

@yanliang567
Copy link
Contributor

This is not a bug, should be a mis-use of pymilvus api, @JackTan25 help check this.

@chasingegg could you please clarify which part is mis-used, and how to correct it>
/assign @chasingegg
/unassign

@JackTan25
Copy link
Author

I find out the api error in my usage. Let's close this one.

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 needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

4 participants