-
Notifications
You must be signed in to change notification settings - Fork 43
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
Search with iterator #286
Comments
Do you really need this feature? if so, I will add it later. |
@shanghaikid well, if there is a workaround where I can return more than |
I see, I will implement this feature. |
@shanghaikid Awesome - thanks. If you could republish @zilliz/milvus2-sdk-node via npm then as well, please. That'd be great. I am using package managers to install it. |
Of course, but it takes time. stay tuned. |
Hi, |
sorry, it's on hold,I've finished the query iterator, but based on my testing, the search iterator is not accurate, I am waiting for milvus team 's response. |
can you give me your case, I can do some extra testing specifically for your case, like what's your schema, which metric do you like to use? |
I need to get all primary keys from all the entities. So right now I am iterating through pagination until there are no more results left. However, the right solution would be to have the iterator |
so all you need is query iterator, not search right? the query iterator is ready, but search is not good. |
Yes, in my case i only need a query iterator. Thx |
ok, I will release one version tomorrow. |
Hi , v2.4.2 is released. please check here to view the usage method: https://github.com/milvus-io/milvus-sdk-node/tree/v2.4.2?tab=readme-ov-file#whats-new-in-v242 |
Hey thx for the quick reply and update. Just one last thing, I have seen that the limit is required but the documentation sais it is optional. Thx!! |
Describe the feature:
It doesn't seem to be possible to "search with iterator" as documented in:
https://milvus.io/docs/v2.3.x/with_iterators.md#Search-with-iterator
Describe a specific use case for the feature:
avoiding:
invalid max query result window, (offset+limit) should be in range [1, 16384]
ERRORThe text was updated successfully, but these errors were encountered: