Another alternative is to use the TermsQueryParser which is intended to deal with very large lists of values that should be ORed together. It may be useful if your query pattern matches its intent. see: https://cwiki.apache.org/confluence/display/solr/Other+Parsers#OtherParsers-TermsQueryParser
Best, Erick On Fri, Aug 5, 2016 at 8:23 AM, Shawn Heisey <[email protected]> wrote: > On 8/3/2016 12:49 AM, liubiaoxin1 wrote: >> set exery core solrconfig.xml: 4096 > > Are you absolutely certain that you have set maxBooleanClauses on > *EVERY* core in that Solr instance? > > This value is global, across the entire JVM, and the last core that > starts will set the value for all cores. > > It is not possible to explicitly control the exact starting order of > your cores. If the config option is missing from the last core that > gets started, then the global setting will be reset back to 1024. > > I tried to address this once, but the change was vetoed, and by Apache's > rules, I wasn't allowed to do it. > > https://issues.apache.org/jira/browse/SOLR-4586 > > I hope to try again and make this situation better for Solr. > > Thanks, > Shawn >
