-
Notifications
You must be signed in to change notification settings - Fork 124
Closed
Labels
good first issueGood for newcomersGood for newcomers
Description
Search params across different engines are structured very differently.
In Qdrant configs, we have:
{ "parallel": 1, "search_params": { "hnsw_ef": 64 } }, { "parallel": 1, "search_params": { "hnsw_ef": 128 } }, { "parallel": 1, "search_params": { "hnsw_ef": 256 } }, { "parallel": 1, "search_params": { "hnsw_ef": 512 } },
In Elasticsearch, we have (no nesting):
{ "parallel": 1, "num_candidates": 64 }, { "parallel": 1, "num_candidates": 128 }, { "parallel": 1, "num_candidates": 256 }, { "parallel": 1, "num_candidates": 256 },
In Milvus config, we have:
{ "parallel": 1, "params": { "ef": 128 } }, { "parallel": 1, "params": { "ef": 256 } }, { "parallel": 1, "params": { "ef": 512 } }
In weaviate configs we have:
{ "parallel": 1, "vectorIndexConfig": { "ef": 64} }, { "parallel": 1, "vectorIndexConfig": { "ef": 128} }, { "parallel": 1, "vectorIndexConfig": { "ef": 256} }, { "parallel": 1, "vectorIndexConfig": { "ef": 512} },
the parallel
field will remain outside but rest need to passed to the engine and it should have the same name (I propose params
). We need to refactor the code accordingly .
Metadata
Metadata
Assignees
Labels
good first issueGood for newcomersGood for newcomers