[
https://issues.apache.org/jira/browse/LUCENE-8983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Drew Foulks updated LUCENE-8983:
--------------------------------
Reporter: Bruno Roustant (was: Bruno Roustant)
> PhraseWildcardQuery - new query to control and optimize wildcard expansions
> in phrase
> -------------------------------------------------------------------------------------
>
> Key: LUCENE-8983
> URL: https://issues.apache.org/jira/browse/LUCENE-8983
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/search
> Reporter: Bruno Roustant
> Assignee: Bruno Roustant
> Priority: Major
> Fix For: 8.4
>
> Time Spent: 3h
> Remaining Estimate: 0h
>
> A generalized version of PhraseQuery, built with one or more MultiTermQuery
> that provides term expansions for multi-terms (one of the expanded terms must
> match).
> Its main advantage is to control the total number of expansions across all
> MultiTermQuery and across all segments.
> This query is similar to MultiPhraseQuery, but it handles, controls and
> optimizes the multi-term expansions.
>
> This query is equivalent to building an ordered SpanNearQuery with a list of
> SpanTermQuery and SpanMultiTermQueryWrapper.
> But it optimizes the multi-term expansions and the segment accesses.
> It first resolves the single-terms to early stop if some does not match.
> Then it expands each multi-term sequentially, stopping immediately if one
> does not match. It detects the segments that do not match to skip them for
> the next expansions. This often avoid expanding the other multi-terms on some
> or even all segments. And finally it controls the total number of expansions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
