[
https://issues.apache.org/jira/browse/LUCENE-998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680854#action_12680854
]
Mark Miller commented on LUCENE-998:
------------------------------------
I think it was understood - it made field cache loading slow because we
attempted to enumerate every unique term for all segments from every individual
segment. Because term/seg drops log, it was incredibly wasteful. You could try
5,000 terms against each of 5 segments when segments 2-5 may have had 3 terms a
piece in them. So I don't think it will be an issue here - we should get a bit
better performance with LUCENE-1483 though, because each multi-term query will
rewrite against each segment - so you won't have huge boolean queries hitting
small segments like before - each multi-term query will 'fit' each segment,
rather than one query hits all.
> 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]
