Return-Path: Delivered-To: apmail-lucene-java-user-archive@www.apache.org Received: (qmail 45813 invoked from network); 8 Dec 2010 13:20:44 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 8 Dec 2010 13:20:44 -0000 Received: (qmail 83192 invoked by uid 500); 8 Dec 2010 13:20:42 -0000 Delivered-To: apmail-lucene-java-user-archive@lucene.apache.org Received: (qmail 83158 invoked by uid 500); 8 Dec 2010 13:20:42 -0000 Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-user@lucene.apache.org Delivered-To: mailing list java-user@lucene.apache.org Delivered-To: moderator for java-user@lucene.apache.org Received: (qmail 24414 invoked by uid 99); 8 Dec 2010 07:06:48 -0000 X-ASF-Spam-Status: No, hits=-2.8 required=10.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_HI,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of rarao2@cisco.com designates 144.254.224.141 as permitted sender) Authentication-Results: ams-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhgFAGK9/kyQ/khLgWdsb2JhbACCBqFFFgEWIiKlO5sgghSDNQSEYIkr X-IronPort-AV: E=Sophos;i="4.59,315,1288569600"; d="scan'208,217";a="14842872" X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CB96A6.58FE2300" Subject: RE: Problem with "BooleanQuery.TooManyClauses" Date: Wed, 8 Dec 2010 12:35:50 +0530 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Problem with "BooleanQuery.TooManyClauses" Thread-Index: AcuWlZrqyNB9f8QhSdulc5T3DSCoMgAEDGKQ From: "Raghavendra D.V Rao (rarao2)" To: "Raghavendra D.V Rao (rarao2)" , , Cc: "Preetham Kajekar (preetham)" X-OriginalArrivalTime: 08 Dec 2010 07:05:51.0539 (UTC) FILETIME=[59323030:01CB96A6] ------_=_NextPart_001_01CB96A6.58FE2300 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Update on my previous query. =20 In our application environment, our queries will typically contain 200-300 clauses. The chances of clauses becoming 5000 is less. =20 Hence we are interested in knowing the actual impact of setting the setMaxClauseCount () to high value on the normal queries, containing less number of clauses. =20 Regards, Raghav =20 From: Raghavendra D.V Rao (rarao2)=20 Sent: Wednesday, December 08, 2010 10:36 AM To: 'java-user@lucene.apache.org'; 'lucene-net-user@lucene.apache.org' Cc: Preetham Kajekar (preetham) Subject: Problem with "BooleanQuery.TooManyClauses" =20 Hi All, =20 We have a requirement where in we need to construct a BooleanQuery, with the TermQueries, whose count is large , but that it is somewhat fixed number. It could be around a 5000 or 6000. =20 At present we are hitting the BooleanQuery.TooManyClauses exception, as the default count of max caluse is 1024. =20 I just wanted to know if there are any performance related impact because of setting this to some high value, using BooleanQuery.setMaxClauseCount(); =20 Please help. =20 Details. Lucene Version =3D 2.4.0 =20 =20 =20 =20 Regards, Raghav =20 ------_=_NextPart_001_01CB96A6.58FE2300--