Yes, that's what I have started to use already. Probably, this is the
easiest solution. Thanks.
On Tue, Jan 17, 2012 at 3:03 AM, Erick Erickson erickerick...@gmail.comwrote:
Why not just up the maxBooleanClauses parameter in solrconfig.xml?
Best
Erick
On Sat, Jan 14, 2012 at 1:41 PM,
Why not just up the maxBooleanClauses parameter in solrconfig.xml?
Best
Erick
On Sat, Jan 14, 2012 at 1:41 PM, Dmitry Kan dmitry@gmail.com wrote:
OK, let me clarify it:
if solrconfig has maxBooleanClauses set to 1000 for example, than queries
with clauses more than 1000 in number will be
OK, let me clarify it:
if solrconfig has maxBooleanClauses set to 1000 for example, than queries
with clauses more than 1000 in number will be rejected with the mentioned
exception.
What I want to do is automatically split such queries into sub-queries with
at most 1000 clauses inside SOLR and
Hello,
The problem seem to have been solved (still some testing is required). But
I stumbled upon another issue.. which requires telling a bit about the use
case.
I would like to by-pass the maxBooleanClauses limit in such a way, that
those queries that contain boolean clauses more than
: I would like to by-pass the maxBooleanClauses limit in such a way, that
: those queries that contain boolean clauses more than maxBooleanClauses in
: the number, would be automatically split into sub-queries. That part is
: done.
:
: Now, when such a query arrives, solr throws
:
:
Hello list,
I need to split the incoming original facet query into a list of
sub-queries. The logic is done and each sub-query gets added into outgoing
queue with rb.addRequest(), where rb is instance of ResponseBuilder.
In the logs I see that along with the sub-queries the original query gets
