Closed NicoYuan1986 closed 1 year ago
@NicoYuan1986 problem1: if metrics type is not set, then sdk side cannot decide the default radius of first page iteration. For normal search operation, metrics type will be set on query node according to the genuine metrics type of index. But if we want to know this info on sdk side, there has to be an extra rpc call to querycoord.
I think all search APIs do not have to specify the metric type in search params, this is one of principles for all the sdk? @czs007 any comments? /assign @czs007
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.
Rotten issues close after 30d of inactivity. Reopen the issue with /reopen
.
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.
Rotten issues close after 30d of inactivity. Reopen the issue with /reopen
.
Is there an existing issue for this?
Environment
Current Behavior
The feature of search_params in search and search_iterator should be consistent.
search_params = {}
is allowed in search, while reports error in search_iterator. example:default value of search list Now we do not need to set search_list while using diskann. failed test case: test_search_iterator_after_different_index_metrics (only fail on pytest now)
Expected Behavior
pass
Steps To Reproduce
No response
Milvus Log
No response
Anything else?
No response