at 3:47 PM, pravesh wrote:
>
>> I'm sure you can fix this by increasing value to some
>> max.
>> This shld apply to filter query as well
>>
>> --
>> View this message in context:
>>
http://lucene.472066.n3.nabble.com/Too-many-Boolean-Clause-and-Filter-Query-tp2974848p2988190.html
>> Sent from the Solr - User mailing list archive at Nabble.com.
>>
max.
> This shld apply to filter query as well
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Too-many-Boolean-Clause-and-Filter-Query-tp2974848p2988190.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
I'm sure you can fix this by increasing value to some
max.
This shld apply to filter query as well
--
View this message in context:
http://lucene.472066.n3.nabble.com/Too-many-Boolean-Clause-and-Filter-Query-tp2974848p2988190.html
Sent from the Solr - User mailing list archive at Nabble.com.
A filter query does not affect the scoring of the document ,so is filter
query like constantScore query and hence should not be affected by the
maxBoolean clause?
Regards
Sujatha
On Mon, May 23, 2011 at 4:56 PM, Sujatha Arun wrote:
> I got the info from this artice
>
>
> http://www.lucidimagi
I got the info from this artice
http://www.lucidimagination.com/blog/2009/06/08/bringing-the-highlighter-back-to-wildcard-queries-in-solr-14/
Yes ,I know this can be configured ,but this will not scale to "n" ,what is
the performance implication of this with "n" Boolean Clauses .
Regards
Sujat
> But this also gives the same TOO many Boolean Caluses
> Exception
You can adjust that parameter in solrconfig.xml
3024
Sujatha,
On Mon, May 23, 2011 at 1:05 PM, Sujatha Arun wrote:
> Then we changed this to a filter query as follows , as filter Query is not
> supposed to result in MaxBoolean Clause Exception
Where did you read this? I'm pretty sure, that both is based on the
same check for the maximum number of
Hello,
We were initially doing a query with multiple "OR" as follows
AND id:(1 2 3 4 5 ...n number )
Which gave maxBoolean Exception on exceeding 1024 boolean operators
Then we changed this to a filter query as follows , as filter Query is not
supposed to result in MaxBoolean Clause