Details
-
Improvement
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
None
-
None
-
None
-
New
Description
Currently we deoptimize when a minimumNumberShouldMatch is provided and fall back to a scorer that doesn't dynamically prune hits based on scores.
Given how WANDScorer and MinShouldMatchSumScorer are similar I wonder if we could remove MinShouldSumScorer once WANDScorer supports minimumNumberShould match. Then any improvements we bring to WANDScorer like two-phase support (LUCENE-8806) would automatically cover more queries.
Attachments
Issue Links
- links to