Shawn, Thanks a lot for your reply. But I am confused again if the following query is complex. http://localhost:8983/solr/test/select/?q=content:*&fl=content&hl=true&hl.fl=content&hl.maxAnalyzedChars=31375&start=64&rows=1&sort=obs_date%20desc
Is that because of content : *? The only unusual thing is the field size of the "content". In this particular case content field has enormously big data. Since this problem comes only when we do a search on * for content field. Is there a way that we can split the doc size? Regards, Sawan From: Shawn Heisey-4 [via Lucene] [mailto:ml-node+s472066n4057027...@n3.nabble.com] Sent: 18 April 2013 PM 09:38 To: Sawan Verma Subject: Re: TooManyClauses: maxClauseCount is set to 1024 On 4/18/2013 6:02 AM, sawanverma wrote: > Hi Yonik, > > Thanks for your reply. > > I tried increasing the maxClauseCount to a bigger value. But what could be > the ideal value and will not that hit the performance? What are the chances > that if we increase the value we will not face this issue again? Changing the maxBooleanClauses value does not affect performance. It's just an arbitrary limit on query complexity. You can make it as big as you want and Solr's performance will not change. For most people, 1024 is plenty. For others, we have no idea how many clauses are needed. The queries themselves with large numbers of clauses are what affects performance, and the only way to improve it is to decrease the query complexity. Chances are good that you are already experiencing the performance hit associated with large queries. Adding more clauses to a query will reduce performance. If you find yourself in a situation where you continually need more boolean clauses, you may need to start over and create a better design. The maxBooleanClauses value is just a safety net, created long ago when Lucene worked differently than it does now. There is a discussion currently happening among committers about whether that limit even needs to exist. Very likely the limit in Solr will be removed in the near future. Thanks, Shawn ________________________________ If you reply to this email, your message will be added to the discussion below: http://lucene.472066.n3.nabble.com/TooManyClauses-maxClauseCount-is-set-to-1024-tp4056965p4057027.html To unsubscribe from TooManyClauses: maxClauseCount is set to 1024, click here<http://lucene.472066.n3.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4056965&code=c2F3YW4udmVybWFAZ2xhc3NiZWFtLmNvbXw0MDU2OTY1fC0xMTI5MDQ2NDY1>. NAML<http://lucene.472066.n3.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> -- View this message in context: http://lucene.472066.n3.nabble.com/TooManyClauses-maxClauseCount-is-set-to-1024-tp4056965p4057060.html Sent from the Solr - User mailing list archive at Nabble.com.
