lucene-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bruno Roustant (Jira)" <j...@apache.org>
Subject [jira] [Commented] (LUCENE-8983) PhraseWildcardQuery - new query to control and optimize wildcard expansions in phrase
Date Thu, 28 Nov 2019 11:49:00 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-8983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16984356#comment-16984356
] 

Bruno Roustant commented on LUCENE-8983:
----------------------------------------

The randomization made only one segment while I thought I ensured 2 segments even with randomization.
To make the test more robust, I improved it to skip special segment test counters and just
focus on query results and scores if there are not exactly 2 segments.

> 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.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org


Mime
View raw message