[
https://issues.apache.org/jira/browse/SOLR-4586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14298708#comment-14298708
]
David Smiley commented on SOLR-4586:
------------------------------------
bq. If eliminating the limit isn't going to happen, then I have the following
proposal, in addition to lowering the default to 64. I think I built this idea
into some of the patch work I did for this issue, but I can no longer remember
for sure: I propose that we include code so that the highest maxBooleanClauses
value seen during core loading become the global value, preventing a lower
value seen later during the load process from overriding it.
+1 !
And the low value is I think a reasonable value. If you hit this, it is likely
you should be using \{!terms}; and the docs near the config value should say
this. If a user query hits this... well 64 is plenty for what most apps might
reasonable expect of a user (but not all apps, I realize).
It would be neat to modify the query parser to automatically introduce Terms
filter in place of a BooleanQuery that is getting too big, so long as the
clauses are all OR clauses. That would be a separate issue though.
> Eliminate the maxBooleanClauses limit
> -------------------------------------
>
> 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, SOLR-4586.patch, SOLR-4586.patch,
> SOLR-4586_verify_maxClauses.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 was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
