You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
in https://milvus.io/docs/index.md?tab=sparse page, remove any contents related of SPARSE_WAND, and mention {"inverted_index_algo": "DAAT_MAXSCORE|DAAT_WAND"} instead. Add description of inverted_index_algo in Index building parameters section.
Limits section: For sparse vector fields, only the SPARSE_INVERTED_INDEX index types are supported.
FAQ section: remove this question Can you explain the difference between, since we have discussed the different algos in Set index params for vector field section in introduction of params.inverted_index_algo.
in Set index params for vector field section, SPARSE_WAND is incorrectly provided in Node.js code example.
remove mentioning of drop_ratio_build. simply search for this keyword in the entire repo and remove it everywhere(both content and code examples). mention only in https://milvus.io/docs/index.md?tab=sparse page that this is deprecated since v2.5.4 and will still be accepted but will no longer have actual effect on the index.
Suggestion
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered:
one more: in https://milvus.io/docs/limitations.md page, now SPARSE_INVERTED_INDEX also support range search, search with iterator and grouping search.
Is there an existing issue for this?
Issue
Index limits on different search types
section{"inverted_index_algo": "DAAT_MAXSCORE|DAAT_WAND"}
instead. Add description of inverted_index_algo inIndex building parameters
section.Can you explain the difference between
, since we have discussed the different algos inSet index params for vector field
section in introduction ofparams.inverted_index_algo
.Set index params for vector field
section,SPARSE_WAND
is incorrectly provided in Node.js code example.Suggestion
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: