[
https://issues.apache.org/jira/browse/LUCENE-9346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17262667#comment-17262667
]
ASF subversion and git services commented on LUCENE-9346:
---------------------------------------------------------
Commit 40cd50a584e860c40de77ef604f2843345613c61 in lucene-solr's branch
refs/heads/branch_8x from Adrien Grand
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=40cd50a ]
LUCENE-9346: Add CHANGES entry.
> 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
> Priority: Minor
> Time Spent: 3h 40m
> Remaining Estimate: 0h
>
> 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
