[
https://issues.apache.org/jira/browse/SOLR-4586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13611411#comment-13611411
]
Jack Krupansky commented on SOLR-4586:
--------------------------------------
This issue has morphed more than a bit since the original proposal to simply
remove the maxBooleanClauses limit from Solr.
At this stage, I'd be more in favor of simply increasing the default
maxBooleanClauses in Solr to 1 million (or whatever), but keeping all of the
other semantics the exact same so that nobody sees any change other than the
larger default limit, and all the rules (crazy as they are) for when and how
the limit gets set remain unchanged. In other words, nobody needs to dig and
try to understand "What does this really mean??" because the new default limit
means quite simply "Don't worry about it."
I'm tempted to push for deprecation and removal of the limit, but I can see
some merit in an artificial limit for testing and to limit resource consumption.
In short, the main goals here are: 1) Make the old limit a non-issue for
typical applications, 2) don't mess with the semantics or create new rules for
where or when or how to set the limit, and 3) preserve the limit capability for
special situations where it is desirable to REUDCE the limit, as opposed to
being forced to increase the limit as some applications need today.
> Increase default maxBooleanClauses
> ----------------------------------
>
> Key: SOLR-4586
> URL: https://issues.apache.org/jira/browse/SOLR-4586
> 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: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
