[
https://issues.apache.org/jira/browse/SOLR-4586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14195112#comment-14195112
]
Robert Parker commented on SOLR-4586:
-------------------------------------
Under Solr 4.10.2 in solrcloud configuration, if I upload a change to
solrconfig.xml to zookeeper that raises maxBooleanClauses from 1024 to 2048 and
then reload the collection, the cores do not recongnize a new value for
maxBooleanClauses unlike other changes to schema.xml and solrconfig.xml. I
have to bounce Solr on each node before queries will honor the new value for
maxBooleanClauses. This seems like unintentional behavior. I should be able
to make any change to schema.xml and solrconfig.xml, then upload those to
zookeeper and have each node in the cluster instantly honor all new values
after a core/collection reload.
> 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, 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]
