Uploaded image for project: 'Lucene - Core'
  1. Lucene - Core
  2. LUCENE-8382

Don't propagate calls to setMinCompetitiveScore in MultiCollector

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 8.0
    • Component/s: None
    • Labels:
      None
    • Lucene Fields:
      New

      Description

      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.

        Attachments

        1. LUCENE-8382.patch
          5 kB
          Adrien Grand

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              jpountz Adrien Grand
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: