[
https://issues.apache.org/jira/browse/LUCENE-6458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14519316#comment-14519316
]
David Smiley commented on LUCENE-6458:
--------------------------------------
Adrien, how did you arrive at BOOLEAN_REWRITE_THRESHOLD=50 ? This reminds me
of when I was working on the Solr "Terms" QParser that supports 3-4 different
options, to include BooleanQuery & TermsQuery. I wanted to have it
automatically use a BooleanQuery at a low term threshold but I wasn't sure what
to use so I didn't bother, and I didn't have time to do benchmarks then. In
hind-site, any hunch value (64?) would have been better then always choosing
TermsQuery no matter what. I have a feeling that the appropriate threshold is
a function of the number of indexed terms, instead of just a constant.
> MultiTermQuery's FILTER rewrite method should support skipping whenever
> possible
> --------------------------------------------------------------------------------
>
> Key: LUCENE-6458
> URL: https://issues.apache.org/jira/browse/LUCENE-6458
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Adrien Grand
> Assignee: Adrien Grand
> Priority: Minor
> Attachments: LUCENE-6458.patch
>
>
> Today MultiTermQuery's FILTER rewrite always builds a bit set fom all
> matching terms. This means that we need to consume the entire postings lists
> of all matching terms. Instead we should try to execute like regular
> disjunctions when there are few terms.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
