Of course there will be performance and memory changes. The only real question is whether your situation can tolerate them. The whole point of maxBooleanClauses is exactly that going above that limit should be a conscious decision because it has implications for both memory and performance
That said, that limit was put in there quite some time ago and things are much faster now. I've seen installation where this limit is raised over 10K. Are you sure this is the best approach though? Could joins work here? Or reranking? (this last is doubtful, but...). This may well be an XY problem, you haven't explained _why_ you need so many conditions which might enable other suggestions. Best, Erick On Mon, Oct 13, 2014 at 9:10 AM, ankit gupta <ankitgupta...@gmail.com> wrote: > hi, > > Can we quantify the impact on SOLR memory usage/performance if we increase > the boolean clause. I am currently using lot of OR clauses in the query > (close to 10K) and can see heap size growing. > > Thanks, > Ankit
