lucene-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (Jira)" <j...@apache.org>
Subject [jira] [Commented] (LUCENE-8983) PhraseWildcardQuery - new query to control and optimize wildcard expansions in phrase
Date Wed, 27 Nov 2019 10:54:00 GMT

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

ASF subversion and git services commented on LUCENE-8983:
---------------------------------------------------------

Commit d764bf345e2789589fbead7df5838dc20247c577 in lucene-solr's branch refs/heads/branch_8x
from Bruno Roustant
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=d764bf3 ]

LUCENE-8983: Add PhraseWildcardQuery to control multi-terms expansions in phrase.


> 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
>          Time Spent: 2h 40m
>  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