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/03/17 15:53:00 UTC

[jira] [Resolved] (LUCENE-10418) Improve Query rewriting for non-scoring clauses

     [ https://issues.apache.org/jira/browse/LUCENE-10418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adrien Grand resolved LUCENE-10418.
-----------------------------------
    Fix Version/s: 9.2
       Resolution: Fixed

> 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
>             Fix For: 9.2
>
>          Time Spent: 1h 50m
>  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-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org