[
https://issues.apache.org/jira/browse/LUCENE-10418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17508252#comment-17508252
]
ASF subversion and git services commented on LUCENE-10418:
----------------------------------------------------------
Commit 1dcb64b492b33f2adc3735458eefbc80e8feb1ef in lucene's branch
refs/heads/main from Adrien Grand
[ https://gitbox.apache.org/repos/asf?p=lucene.git;h=1dcb64b ]
LUCENE-10418: Move CHANGES to the correct section.
> Improve Query rewriting for non-scoring clauses
> -----------------------------------------------
>
> Key: LUCENE-10418
> URL: https://issues.apache.org/jira/browse/LUCENE-10418
> Project: Lucene - Core
> Issue Type: Task
> Reporter: Adrien Grand
> Priority: Minor
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Query rewriting is occasionally important for performance, e.g. it may allow
> using an optimized bulk scorer instead of the default bulk scorer like in the
> example from LUCENE-10412.
> One case when we could simplify queries is in the non-scoring case. All
> layers of query wrappers that only affect scoring like BoostQuery and
> ConstantScore query can be removed, which might help identify new
> opportunities for rewriting. For instance, we have several rewrite rules that
> optimize for MatchAllDocsQuery and would fail to recognize it if it is behind
> a ConstantScoreQuery or a BoostQuery. Boolean queries can also simplify
> themselves in the non-scoring case, by changing MUST clauses to FILTER
> clauses, or removing fully optional SHOULD clauses.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
