[
https://issues.apache.org/jira/browse/SOLR-13090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16734225#comment-16734225
]
ASF subversion and git services commented on SOLR-13090:
--------------------------------------------------------
Commit 73797f60ada12aa2a09180947d4bdf556a234fea in lucene-solr's branch
refs/heads/master from Jason Gerlowski
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=73797f6 ]
SOLR-13090: Add missing CHANGES.txt entry
> Make maxBooleanClauses support system-property override
> -------------------------------------------------------
>
> Key: SOLR-13090
> URL: https://issues.apache.org/jira/browse/SOLR-13090
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: master (8.0), 7.7
> Reporter: Jason Gerlowski
> Assignee: Jason Gerlowski
> Priority: Minor
> Fix For: master (8.0), 7.7
>
> Attachments: SOLR-13090.patch
>
>
> Currently, the {{maxBooleanClauses}} property is specified in most
> solrconfig's as the hardcoded value "1024". It'd be nice if we changed our
> shipped configs so that they instead specified it as
> {{<maxBooleanClauses>${solr.max.booleanClauses:1024}</maxBooleanClauses}}.
> This would maintain the current OOTB behavior (maxBooleanClauses would still
> default to 1024) while adding the ability to update maxBooleanClauses values
> across the board much more easily. (I see users want to do this often when
> they first run up against this limit.)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
