[
https://issues.apache.org/jira/browse/SOLR-17928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18034164#comment-18034164
]
Puneet Ahuja commented on SOLR-17928:
-------------------------------------
[~hossman]Thanks for these valuable comments, have taken care of these in my
latest commit, and have also added to the "Major Changes in Solr 10".
Previously, improving accuracy required increasing topK (which returns more
results), but efSearch enables exploring more candidates while still receiving
exactly topK results. And default efSearch is 2*topK.
ElasticSearch also has a similar parameter called num_candidates which achieves
something similar, and they default to 1.5*topK.
Link:
https://www.elastic.co/docs/reference/query-languages/query-dsl/query-dsl-knn-query
> Add efSearch parameter to knn query
> -----------------------------------
>
> Key: SOLR-17928
> URL: https://issues.apache.org/jira/browse/SOLR-17928
> Project: Solr
> Issue Type: Improvement
> Components: vector-search
> Reporter: Ishan Chattopadhyaya
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Right now, only topK can be requested. efSearch is a standard overfetch
> parameter.
> Proposing that we add it for better recall accuracy.
> (FYI, Elasticsearch calls it num_candidates. Commonly referred to as
> efSearch, similar to efConstruction that we call beamWidth)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
