[
https://issues.apache.org/jira/browse/SOLR-4586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16052529#comment-16052529
]
Erick Erickson commented on SOLR-4586:
--------------------------------------
Making it per-core would go a long way to making it easier to support clients.
Having a default limit isn't the problem, it's perfectly supportable to tell a
client "This a built in safety valve to prevent runaway queries that you can
change at need, we just want it be a conscious decision on your part".
What's not so supportable (or explainable for that matter) is that the last
core loaded wins, and I can't tell them which one would win. Or even that the
same one will win all the time. We have multiple threads loading cores in Solr,
so the order of execution of a node with a bunch of cores isn't determinant.
Or worse, it works on one node but not another because cores using a different
config file happened to be loaded last on the machines. Or, much worse, "Search
just stopped working with too many boolean clauses exceptions".
If we have any limit, I'd prefer it to be left in the solrconfig files we
distribute. Clients can find it themselves that way.
> 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]
