Return-Path: Delivered-To: apmail-jakarta-lucene-dev-archive@www.apache.org Received: (qmail 52424 invoked from network); 8 Nov 2004 09:33:58 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 8 Nov 2004 09:33:58 -0000 Received: (qmail 73624 invoked by uid 500); 8 Nov 2004 09:33:55 -0000 Delivered-To: apmail-jakarta-lucene-dev-archive@jakarta.apache.org Received: (qmail 73596 invoked by uid 500); 8 Nov 2004 09:33:54 -0000 Mailing-List: contact lucene-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Lucene Developers List" Reply-To: "Lucene Developers List" Delivered-To: mailing list lucene-dev@jakarta.apache.org Received: (qmail 73582 invoked by uid 99); 8 Nov 2004 09:33:53 -0000 X-ASF-Spam-Status: No, hits=0.1 required=10.0 tests=NO_REAL_NAME,UPPERCASE_25_50 X-Spam-Check-By: apache.org Received: from [192.18.33.10] (HELO exchange.sun.com) (192.18.33.10) by apache.org (qpsmtpd/0.28) with SMTP; Mon, 08 Nov 2004 01:33:53 -0800 Received: (qmail 17240 invoked by uid 50); 8 Nov 2004 09:33:52 -0000 Date: 8 Nov 2004 09:33:52 -0000 Message-ID: <20041108093352.17239.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: lucene-dev@jakarta.apache.org Cc: Subject: DO NOT REPLY [Bug 32109] - Spurious TooManyClauses error X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32109 Spurious TooManyClauses error jakarta@ehatchersolutions.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME ------- Additional Comments From jakarta@ehatchersolutions.com 2004-11-08 09:33 ------- This behavior by design. The issue is that BooleanQuery has a default limit of 1024 clauses. In your case, you're using a date range that expands to more than this number. Two options that immediately come to mind are to increase the number of allowed boolean clauses (at the expense of resources used during the query) or to index (and query) a field by year (or quarter) such that there are far fewer terms that match. --------------------------------------------------------------------- To unsubscribe, e-mail: lucene-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: lucene-dev-help@jakarta.apache.org