Hi Shalin, Thanks for your time to respond to this issue. 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. Thanks, Dipanjan ________________________________ From: Shalin Shekhar Mangar <shalinman...@gmail.com> Reply-To: <solr-user@lucene.apache.org> Date: Mon, 20 Jul 2009 13:58:55 +0530 To: <solr-user@lucene.apache.org> Subject: Re: Help needed with Solr <maxBooleanClauses> On Mon, Jul 20, 2009 at 1:37 PM, dipanjan_pramanick < dipanjan_praman...@infosys.com> wrote: > Hi, > We have scenario where we need to send more than 1024 ids in the Solr url > as "OR" condition. > I have changed the value of maxBooleanClauses in solrconfig.xml, to 2048, > but it is failing after handling 1024 "OR" conditions. > Solr is throwing "SEVERE: org.apache.solr.common.SolrException: Bad > Request" whenever I am sending more than 1024 OR conditions. Is there any > way I can change this value on Solr configuration. The maxBooleanClauses is there as a safe guard against extremely slow queries. If you can tell us about the exact problem you are solving, we may be able to suggest an alternative approach? Creating such huge boolean clauses may be a bad design choice. As for the exception you are seeing, it seems to me that you may be exceeding the size of a GET request. Using an HTTP POST request may work. -- 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***
