Currently, if a user sets a parameter at the wrong level in search_params, it will silently fail to take effect. Milvus does not currently validate or warn about such misconfigurations, which can lead to confusing behavior.
To prevent such situations, we plan to simplify the structure of search_params by flattening it into a single-layer parameter list. This approach will eliminate concerns about whether parameters are placed in the correct hierarchy.
Why is this needed?
No response
Anything else?
This is a compatible logic: previous behavior will still be supported, but in the future, we will guide users through documentation to adopt a single-layer search_params structure.
This should be fixed in Milvus 2.5.x.
Is there an existing issue for this?
What would you like to be added?
Currently, if a user sets a parameter at the wrong level in search_params, it will silently fail to take effect. Milvus does not currently validate or warn about such misconfigurations, which can lead to confusing behavior.
To prevent such situations, we plan to simplify the structure of search_params by flattening it into a single-layer parameter list. This approach will eliminate concerns about whether parameters are placed in the correct hierarchy.
Why is this needed?
No response
Anything else?
This is a compatible logic: previous behavior will still be supported, but in the future, we will guide users through documentation to adopt a single-layer search_params structure. This should be fixed in Milvus 2.5.x.