lucene-dev mailing list archives

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


Mark Miller commented on SOLR-4586:

bq. Even the default I've proposed is probably too high, but what value will work? 

I don't think it's a very good argument because of this silly guessing. We could try and protect
a user from these silly situations everywhere. Should we also limit the number of filters
allowed in an analyzer? Should we watch how many docs you are putting into the index? Should
we make sure you don't add a query filter thats too long and crazy? It's a silly direction
to go down. And that's why you won't find it anywhere else. This is an aberration thats been
around before pretty much any of us showed up. The idea that this is helpful to users is absurd
- I've been around lucene and solr and users for too long to fall for that.
> 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