Hi Shalin,

We just found that there is no limit on Solr side about the maximum boolean 
condition. We have set the <maxBooleanClauses>2048</maxBooleanClauses> and we 
are able to send about 1574 OR conditions.
Over that limit, we are getting "HTTP/1.1 400 Bad Request".

You are correct, it's not a Solr issue, its due to HTTP GET is not being able 
to send such a large request.

But now the question is, Solr only accepts request in url form not as request 
parameter or request object. That's the main issue. Hence we need to send the 
query in url form only.
Can you please suggest, if you have tried the similar thing instead of passing 
as URL, instead passing as object or request entity using POST.



Thanks,
Dipanjan


________________________________
From: Shalin Shekhar Mangar <shalinman...@gmail.com>
Reply-To: <solr-user@lucene.apache.org>
Date: Mon, 20 Jul 2009 14:54:04 +0530
To: <solr-user@lucene.apache.org>
Subject: Re: Help needed with Solr <maxBooleanClauses>

On Mon, Jul 20, 2009 at 2:12 PM, dipanjan_pramanick <
dipanjan_praman...@infosys.com> wrote:

>
> Its true that there is a design flaw, because of what we need to support a
> huge list of OR conditions through Solr.
> But still I would like to know if there is any other configuration other
> than the one in solrConfig.xml, through which we can pass more than 1024 OR
> conditions.
>
> <maxBooleanClauses>1024<maxBooleanClauses>
>
>
> Regarding HTTP Post, in Solr 1.3, it is only accepts request in url form
> not as request parameter or request object. That's another issue. Hence we
> need to send the query in url form only.
>
>
Changing the value of maxBooleanClauses in solrconfig.xml is sufficient. The
problem here is that you may be exceeding the maximum allowed size of an
HTTP GET request (is that 2KB?). You must use POST request to send such a
huge query string. Again, it will help if you can post the complete stack
trace of the error.

--
Regards,
Shalin Shekhar Mangar.


**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely 
for the use of the addressee(s). If you are not the intended recipient, please 
notify the sender by e-mail and delete the original message. Further, you are 
not 
to copy, disclose, or distribute this e-mail or its contents to any other 
person and 
any such actions are unlawful. This e-mail may contain viruses. Infosys has 
taken 
every reasonable precaution to minimize this risk, but is not liable for any 
damage 
you may sustain as a result of any virus in this e-mail. You should carry out 
your 
own virus checks before opening the e-mail or attachment. Infosys reserves the 
right to monitor and review the content of all messages sent to or from this 
e-mail 
address. Messages sent to or from this e-mail address may be stored on the 
Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***

Reply via email to