You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Adrien Grand (Jira)" <ji...@apache.org> on 2022/06/20 12:10:00 UTC
[jira] [Resolved] (LUCENE-10618) Implement BooleanQuery rewrite rules based for minimumShouldMatch
[ https://issues.apache.org/jira/browse/LUCENE-10618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adrien Grand resolved LUCENE-10618.
-----------------------------------
Fix Version/s: 9.3
Resolution: Fixed
Thanks [~joe hou]!
> 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
> Fix For: 9.3
>
> 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: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org