> Now regarding the maxBooleanClauses - how it effects performance (response
> times, memory usage) when increasing it?
Changing maxBooleanClauses doesn't make any difference at all. Having
thousands of clauses is what makes things run slower and take more memory.
The setting just causes large que
first of all thanks for response!
Regarding two tokenizers - it's ok.
switching to NGramFilterFactory didn't help (though I didn't reindex but
don't think it was needed since switched it into 'query' section).
Now regarding the maxBooleanClauses - how it effects performance (response
times, memor
On 5/22/2013 6:43 AM, adm1n wrote:
> SyntaxError: Cannot parse
> 'name:Bbbbm'
The subject mentions one error, the message says another. If you are
getting too many boolean clauses, then you need to increase the
maxBooleanC
From: Mark Miller [mailto:markrmil...@gmail.com]
> Sent: Thursday, October 22, 2009 6:31 PM
> To: solr-user@lucene.apache.org
> Subject: Re: Too Many Boolean Clauses
>
> Giovanni Fernandez-Kincade wrote:
>
>> Hi,
>> I'm trying to perform a search against an inte
ginal Message-
From: Mark Miller [mailto:markrmil...@gmail.com]
Sent: Thursday, October 22, 2009 6:31 PM
To: solr-user@lucene.apache.org
Subject: Re: Too Many Boolean Clauses
Giovanni Fernandez-Kincade wrote:
> Hi,
> I'm trying to perform a search against an integer field
Giovanni Fernandez-Kincade wrote:
> Hi,
> I'm trying to perform a search against an integer field with a ton of OR
> statements for each of the unique values that I want to search for. I pasted
> an example at the bottom of this email. Solr fires back the following error:
> org.apache.lucene.quer
