Return-Path: Delivered-To: apmail-lucene-java-user-archive@www.apache.org Received: (qmail 38123 invoked from network); 15 Jun 2006 16:16:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 15 Jun 2006 16:16:53 -0000 Received: (qmail 52534 invoked by uid 500); 15 Jun 2006 16:16:45 -0000 Delivered-To: apmail-lucene-java-user-archive@lucene.apache.org Received: (qmail 52501 invoked by uid 500); 15 Jun 2006 16:16:45 -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 Received: (qmail 52438 invoked by uid 99); 15 Jun 2006 16:16:45 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Jun 2006 09:16:45 -0700 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [217.12.10.200] (HELO web25902.mail.ukl.yahoo.com) (217.12.10.200) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 15 Jun 2006 09:16:44 -0700 Received: (qmail 55492 invoked by uid 60001); 15 Jun 2006 16:16:22 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.co.uk; h=Message-ID:Received:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=jToMCdnVrTsrfbgO1LyrOT1O3etrH6IuzU3Hyj5G7RkU4JuBRiIJOhSfl6mRc2BuQopsPC/K+1uM/F6S5HVE4hc/5A+TR6dhMSUG+axBleYYPY9YYezZyHDMRUI7XSkWapfMMhOz8WcPSydddHZg7UAmPTtw7q7m8+5KZ6rb0Os= ; Message-ID: <20060615161622.55490.qmail@web25902.mail.ukl.yahoo.com> Received: from [84.131.241.249] by web25902.mail.ukl.yahoo.com via HTTP; Thu, 15 Jun 2006 16:16:22 GMT Date: Thu, 15 Jun 2006 16:16:22 +0000 (GMT) From: eks dev Reply-To: eks dev Subject: Re: BooleanQuery.TooManyClauses on MultiSearcher To: java-user@lucene.apache.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Did not check it, but solr is using SkippingFilter which is not yet commited in Lucene... so this will maybe not work? By the way, any reason today not to commit SkippingFilter to Lucene? I actually see nothing to do for this, but to commit existing SkippingFilter. If there is something I do not mind to spend a few hours to help ----- Original Message ---- From: Chris Hostetter To: java-user@lucene.apache.org Sent: Thursday, 15 June, 2006 5:49:42 PM Subject: RE: BooleanQuery.TooManyClauses on MultiSearcher : I guess the most expensive thing I'm doing from the perspective of Boolean : clauses is heavily using PrefixQuery. : : I want my user to be able to find e-mail to, cc or from james@anydomain, so : I opted for PrefixQuery on James. Bearing in mind that this is causing me : grief with BooleanQuery.TooManyClauses on my MultiSearcher, is there a : smarter approach that I should be adopting? if the only reason you are using a PrefixQuery is so that searchinging for "james" matches "james@domain.com" then i think MDC is right, split that field up (or have one field, but put three terms in "james", "domain.com" and "james@domain.com") .. but if you genuinely need flexible PrefixQuery support, you may want to look at the ConstantScorePrefixQuery in Solr ... there's nothing Solr specific about it, so you could drop it into your Lucene installation. I'm not entirely sure how well the ConstantScoreQueries work with a MultiSearcher (mainly because i odn't know how well Filter's work with MultiSearchers) but you could give it a try -- it certainly won't have a TooManyClauses problem. : : -----Original Message----- : From: Rob Staveley (Tom) [mailto:rstaveley@seseit.com] : Sent: 15 June 2006 14:51 : To: java-user@lucene.apache.org : Subject: BooleanQuery.TooManyClauses on MultiSearcher : : I've just added a 3rd index directory (i.e. 3rd IndexSearcher) to my : MultiSearcher and I'm getting BooleanQuery.TooManyClauses errors on queries : which were working happily on 2 indexes. : : Here's an example query, which hopefully you'll find self-explanatory from : the XML structure. : --------8<-------- : : : : james : james : james : james : james : : james : james : : : --------8<-------- : : Note that there isn't even a range in there. : : Do BooleanQueries not scale well across indexes? : -Hoss --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org For additional commands, e-mail: java-user-help@lucene.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org For additional commands, e-mail: java-user-help@lucene.apache.org