-
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]: metric type not match: invalid [expected=][actual=IP]: invalid parameter #34422
Comments
@cuonglp1713 could you please share the code snippet to reproduce the issue? My guess is that you should specify the same metric type when building index and searching /assign @cuonglp1713 |
@yanliang567 I set same metric_type for both sure. Here is my code:
Btw, even if I forgot set metric_type when creating collection, I expected seeing it in my error logs |
|
|
When I ran the code snippet as you suggested above, I got error msg about "collection not loaded" or "index not found", which I think could be expected. So did you manually build index and load the collection? could you share a completed reproduce code snippet, I am asking that because there are 2 mode for create collection in milvus client sdk. please refer to https://milvus.io/docs/manage-collections.md for details. @cuonglp1713 |
@yanliang567 Sorry beause I just share ideas to prove that I had set metric type for both create and search collection. If you would like to ran code snippet, here is my code:
|
so you did not manually create index and load the collection before searching? could you please try to describe the index? |
I follow to this instruction: https://milvus.io/docs/single-vector-search.md. I search right after insert to Milvus |
@yanliang567
|
I don't think you are doing the same the single-vector-search.md: you customized a schema when creating collection, which leads you have to manually create index and load. please try to milvus_client.describe_index(collection_name, vector_field_name) to check the index params |
https://milvus.io/docs/manage-collections.md please try to read this doc to understand the difference between 2 creation mode |
I will. Thank you for your support. Im close this issue now. |
Helpful !! |
How did you solve it? |
I was having a similar issue where I was looking to filter by date (epoch). This is how I ended doing it:
|
Is there an existing issue for this?
Environment
Current Behavior
I can not use search function of milvus_client because of metric_type. It's not about metric type not match. It is not input expected metric type. Therefore, it's always raise the error metric type not match: invalid [expected=][actual=IP]: invalid parameter. Also I have specify metric_type in milvus_client.create_collection
Expected Behavior
Show metric_type of expected
Steps To Reproduce
No response
Milvus Log
RPC error: [search], <MilvusException: (code=1100, message=fail to search: metric type not match: invalid [expected=][actual=IP]: invalid parameter)>, <Time:{'RPC start': '2024-07-04 11:17:30.777485', 'RPC error': '2024-07-04 11:17:30.778573'}>
Anything else?
No response
The text was updated successfully, but these errors were encountered: