[
https://issues.apache.org/jira/browse/LUCENE-6513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16077300#comment-16077300
]
nishant mehta commented on LUCENE-6513:
---------------------------------------
Here's another approach we tried for limiting the MTQ expansion of span
queries. FrequentTermsScoringRewrite collects terms using the
ParallelArraysTermCollector in ScoringRewrite which is then added to the
PriorityQueue in FrequentTermsScoringRewrite, overflows in the PriorityQueue
are handled using the predicate supplied to FrequentTermsScoringRewrite. The
default is DF_ORDER, but there's also a DF_THEN_TTF_ORDER provided for ties,
and others could be added if needed. Then SpanQueryFrequentTermsScoringRewrite
simply builds a SpanOrQuery out of the collected terms. [~romseygeek] the test
is inspired from your earlier patch. Thanks [~dsmiley] for your prior feedback
on this.
> Allow limits on SpanMultiTermQueryWrapper expansion
> ---------------------------------------------------
>
> Key: LUCENE-6513
> URL: https://issues.apache.org/jira/browse/LUCENE-6513
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Alan Woodward
> Priority: Minor
> Attachments: LUCENE-6513.patch, LUCENE-6513.patch, LUCENE-6513.patch
>
>
> SpanMultiTermQueryWrapper currently rewrites to a SpanOrQuery with as many
> clauses as there are matching terms. It would be nice to be able to limit
> this in a slightly nicer way than using TopTerms, which for most queries just
> translates to a lexicographical ordering.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
