You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@lucene.apache.org by "Adrien Grand (JIRA)" <ji...@apache.org> on 2018/07/04 07:09:00 UTC

[jira] [Created] (LUCENE-8382) Don't propagate calls to setMinCompetitiveScore in MultiCollector

Adrien Grand created LUCENE-8382:
------------------------------------

             Summary: Don't propagate calls to setMinCompetitiveScore in MultiCollector
                 Key: LUCENE-8382
                 URL: https://issues.apache.org/jira/browse/LUCENE-8382
             Project: Lucene - Core
          Issue Type: Improvement
            Reporter: Adrien Grand


Currently it is propagated, which means that one collector can hide hits to another collector. We could try to reconcile min scores across collectors to take the maximum min score, but I don't think it's worth the effort as combinations are most often going to include one collector that needs top hits and another one that doesn't need scores at all (eg. facets or total hits) rather than another collector that also needs top scoring documents.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org