[
https://issues.apache.org/jira/browse/SOLR-4586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16052994#comment-16052994
]
Yonik Seeley commented on SOLR-4586:
------------------------------------
OK one more try: We can get the effect of LUCENE-7880 (elimination of the
static nature of this setting), if we set the static to MAX_INT and do the
max_clause checking ourselves (this can still default to 1024 in the
solrconfig.xml for the core).
This would mean that going over 1024 clauses would still throw an exception by
default (that would be unchanged), but max_clauses would truly become a
per-core setting, or even a per-handler setting in the future if someone wants
to implement that.
Since this fixes the "last-core-wins" staticness bug, while otherwise
preserving existing behavior, I assume no one would be against this?
> Eliminate the maxBooleanClauses limit
> -------------------------------------
>
> Key: SOLR-4586
> URL: https://issues.apache.org/jira/browse/SOLR-4586
> Project: Solr
> Issue Type: Improvement
> Components: search
> Affects Versions: 4.2
> Environment: 4.3-SNAPSHOT 1456767M - ncindex - 2013-03-15 13:11:50
> Reporter: Shawn Heisey
> Fix For: master (7.0)
>
> 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.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
