On Wed, Oct 18, 2017 at 12:23 PM, Erick Erickson <erickerick...@gmail.com> wrote: > What have you tried? And what is the current setting? > > This usually occurs when you are assembling very large OR clauses, > sometimes for ACL calculations. > > So if you have a query of the form > q=field:(A OR B OR C OR........) > or > fq=field:(A OR B OR C OR........) > > change it to use TermsQueryParser, see > https://lucene.apache.org/solr/guide/6_6/other-parsers.html it doesn't > suffer this limitation. > > In recent versions of Solr this is automatic.
Yeah, that was implemented in 6.4, when we know we don't need scoring. So it will be automatic for things like "fq" parameters, but not "q" unless you wrap it in a filter() -Yonik > > Best, > Erick > > On Wed, Oct 18, 2017 at 7:44 AM, Patrick R. TOKOUO <ptok...@gmail.com> wrote: >> Hello, >> Please I have unsuccessfuly tried to fix this error on Solr 6.4. >> I have increased <maxBooleanClauses> value to some max, but the same error >> appear. >> Please, could you help me. >> >> Regards, >> Patrick R. TOKOUO >> Mob: (+237) 6 90 08 55 95 >> Skype: ptokouo >> In: www.linkedin.com/in/patricktokouo >> >> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> >> Garanti >> sans virus. www.avg.com >> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> >> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
