Adrien Grand created LUCENE-9346:
------------------------------------
Summary: WANDScorer should support minimumNumberShouldMatch
Key: LUCENE-9346
URL: https://issues.apache.org/jira/browse/LUCENE-9346
Project: Lucene - Core
Issue Type: Improvement
Reporter: Adrien Grand
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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
