Closed wwli05 closed 1 week ago
please try the code snippet below, or share some code for reproduction
search_params = {
"metric_type": "IP",
"params": {"nprob": 128}
}
# Search with limit
res = client.search(
collection_name="test_collection",
data=data,
limit=3,
search_params=search_params
)
/assign @wwli05 /unassign
pls check below code curl --location --request POST "http://${}/v2/vectordb/entities/search" \ --header "" \ --data-raw '{ "collectionName":"", "data": [], "annsField": "vector", "searchParams": [ "metricType":"IP", "params":{ "nprobe":16 ---we adjust this value, but the performance has no impact, it seems this param does not take effect in Rest V2 ] }'
/assign @PowderLi can you check on that?
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
.
/reopen
@wwli05: Reopened this issue.
Is there an existing issue for this?
Environment
Current Behavior
1.in code [internal/distributed/proxy/httpserver/handler_v2.go], SearchReqV2 struct contains filed [params] , but in restful v2 tutorial section it declares [searchParams] which does not seem match; 2.if i want to declare special param just like [nprobe](FOR IVF_FLAT index) in [params], it does not take effect when i follows the next code in [handler_v2.go]
Expected Behavior
when I declare special search param, it takes effect so that I can take controll of various query params.
Steps To Reproduce
No response
Milvus Log
No response
Anything else?
No response