[ https://issues.apache.org/jira/browse/SOLR-13090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Gerlowski resolved SOLR-13090. ------------------------------------ Resolution: Fixed Fix Version/s: 7.7 master (8.0) > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org