[
https://issues.apache.org/jira/browse/SOLR-4586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13611742#comment-13611742
]
Yonik Seeley commented on SOLR-4586:
------------------------------------
bq. when it really should be in solr.xml, since it cannot be applied per-core.
If it were truly a limit that one would want applied to all cores, then it
should be in solr.xml
But I don't think that's the case. The real bug here is this global static
(max clauses) that has always had far reaching effects.
I'd like to just set the limit to Integer.MAX_VALUE (essentially removing the
limit), but it's not clear if that has any negative effects.
I'm not concerned with any user queries that explicitly have many terms, but am
concerned about MultiTerm queries or other things that Lucene may do internally
based on this number.
For example, in TopTermsRewrite:
{code}
/** return the maximum size of the priority queue (for boolean rewrites this
is BooleanQuery#getMaxClauseCount). */
protected abstract int getMaxSize();
{code}
> 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: [email protected]
For additional commands, e-mail: [email protected]
