[
https://issues.apache.org/jira/browse/LUCENE-998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12681088#action_12681088
]
Justus Pendleton commented on LUCENE-998:
-----------------------------------------
In our case, we are more concerned about the memory usage -- with queries being
rewritten to Boolean queries with over a hundred thousand clauses -- than the
query execution time (though, obviously the execution time is also likely to be
a factor at some point when trying to keep a UI responsive and not have
hundreds of threads gathering massive result sets that are no longer relevant).
We had a similar problem in the past with range queries and the introduction of
the constant range query solved that problem for us, so a constant score
rewrite should also work in this situation.
> 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]
