[
https://issues.apache.org/jira/browse/LUCENE-998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680830#action_12680830
]
Michael McCandless commented on LUCENE-998:
-------------------------------------------
bq. The boolean rewrite is a fairly poor method for multi-term queries. It just
doesn't scale well.
I agree, though I'm unsure how much better constant-score-rewrite mode
scales. Has anyone tested this? (Both enumerate N TermDocs, one in
parallel and the other serially).
I think in 3.0 we should make constant-score rewrite the default?
I'll open a separate issue for this.
But, I'm not sure constant-score rewrite helps with the use case
Justus raised: with constant-score rewrite, there's no way to say
"abort the query if it hits too many terms", which the max clause
count would enable.
> BooleanQuery.setMaxClauseCount(int) is static
> ---------------------------------------------
>
> Key: LUCENE-998
> URL: https://issues.apache.org/jira/browse/LUCENE-998
> Project: Lucene - Java
> Issue Type: Bug
> Components: Search
> Affects Versions: 2.1
> Reporter: Tim Lebedkov
> Attachments: lucene-998.patch
>
>
> BooleanQuery.setMaxClauseCount(int) is static. It does not allow searching in
> multiple indices from different threads using different settings. This
> setting should be probably moved in to the IndexSearcher.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
