lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Smiley (JIRA)" <>
Subject [jira] [Commented] (SOLR-4586) Increase default maxBooleanClauses
Date Fri, 05 Apr 2013 14:14:16 GMT


David Smiley commented on SOLR-4586:

bq. For Lucene, choosing TermsFilter is probably a viable solution much of the time, but this
issue is for Solr. It's linked to a similar issue for Lucene. My Lucene knowledge is very
pitiful, I know enough to be dangerous but not useful. In my head, I imagine that reworking
Solr to eliminate/reduce the use of BooleanQuery is a monumental task. Am I right about that?

The solr user would be un-impacted because they very well may choose to ignore the warning.
 If they have some basic Lucene knowledge, they could write a QParser that builds a ConstantScoreQuery
from a TermsFilter.  It's a piece of cake and if I wasn't so darned busy I'd do it myself
because it's something Solr should have.
> Increase default maxBooleanClauses
> ----------------------------------
>                 Key: SOLR-4586
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>    Affects Versions: 4.2
>         Environment: 4.3-SNAPSHOT 1456767M - ncindex - 2013-03-15 13:11:50
>            Reporter: Shawn Heisey
>         Attachments: SOLR-4586.patch, SOLR-4586.patch, SOLR-4586.patch, SOLR-4586.patch
> In the #solr IRC channel, I mentioned the maxBooleanClauses limitation to someone asking
a question about queries.  Mark Miller told me that maxBooleanClauses no longer applies, that
the limitation was removed from Lucene sometime in the 3.x series.  The config still shows
up in the example even in the just-released 4.2.
> Checking through the source code, I found that the config option is parsed and the value
stored in objects, but does not actually seem to be used by anything.  I removed every trace
of it that I could find, and all tests still pass.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message