lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justus Pendleton (JIRA)" <>
Subject [jira] Commented: (LUCENE-998) BooleanQuery.setMaxClauseCount(int) is static
Date Wed, 11 Mar 2009 23:16:50 GMT


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

> BooleanQuery.setMaxClauseCount(int) is static
> ---------------------------------------------
>                 Key: LUCENE-998
>                 URL:
>             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:
For additional commands, e-mail:

View raw message