[
https://issues.apache.org/jira/browse/LUCENE-998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680838#action_12680838
]
Mark Miller commented on LUCENE-998:
------------------------------------
Ive seen and seen reported, that the constant score version scales *much*
better. Which makes me think the enumeration is not the main problem - on a
pretty large index, I've seen the difference as fairly dramatic - say the
boolean version was in the 10-20 seconds range, the constant score version a
couple seconds type of thing.
I do think constant score should be the default eventually.
Longer term, I would hope you never have to limit the number of terms it can
hit - perhaps just use the timeout collector? I have no real argument against
this patch, just a string I am not interested in tugging myself.
> 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: [email protected]
For additional commands, e-mail: [email protected]
