[
https://issues.apache.org/jira/browse/LUCENE-10618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17556345#comment-17556345
]
ASF subversion and git services commented on LUCENE-10618:
----------------------------------------------------------
Commit bb1b3dce04c06e7533b2ff418b8b7c2544534e24 in lucene's branch
refs/heads/branch_9x from JoeHF
[ https://gitbox.apache.org/repos/asf?p=lucene.git;h=bb1b3dce04c ]
LUCENE-10618: Implement BooleanQuery rewrite rules based for minimumShouldMatch
(#965)
> Implement BooleanQuery rewrite rules based for minimumShouldMatch
> -----------------------------------------------------------------
>
> Key: LUCENE-10618
> URL: https://issues.apache.org/jira/browse/LUCENE-10618
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Adrien Grand
> Priority: Minor
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> While looking into a test failure I noticed that we sometimes create weights
> for boolean queries with no SHOULD clauses and a non-zero
> minimumNumberShouldMatch.
> We could rewrite BooleanQuery to MatchNoDocsQuery when the number of SHOULD
> clauses is less than minimumNumberShouldMatch, and make SHOULD clauses
> required when the number of SHOULD clauses is equal to
> minimumNumberShouldMatch.
> This feels a bit like a degenerate case (why would the use create such a
> query in the first place?) but this case can also happen to non-degenerate
> queries if some SHOULD clauses rewrite to a MatchNoDocsQuery and get removed
> through rewrite.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
