Return-Path: Delivered-To: apmail-lucene-java-user-archive@www.apache.org Received: (qmail 59449 invoked from network); 15 Jun 2006 17:28:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 15 Jun 2006 17:28:48 -0000 Received: (qmail 87736 invoked by uid 500); 15 Jun 2006 17:28:37 -0000 Delivered-To: apmail-lucene-java-user-archive@lucene.apache.org Received: (qmail 87694 invoked by uid 500); 15 Jun 2006 17:28:37 -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 87670 invoked by uid 99); 15 Jun 2006 17:28:37 -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 10:28:37 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [169.229.70.167] (HELO rescomp.berkeley.edu) (169.229.70.167) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Jun 2006 10:28:34 -0700 Received: by rescomp.berkeley.edu (Postfix, from userid 1007) id 9282E5B764; Thu, 15 Jun 2006 10:28:14 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by rescomp.berkeley.edu (Postfix) with ESMTP id 8D38B7F403 for ; Thu, 15 Jun 2006 10:28:14 -0700 (PDT) Date: Thu, 15 Jun 2006 10:28:14 -0700 (PDT) From: Chris Hostetter To: java-user@lucene.apache.org Subject: RE: BooleanQuery.TooManyClauses on MultiSearcher In-Reply-To: <20060615162546.0A608187B4@mail.seseit.com> Message-ID: References: <20060615162546.0A608187B4@mail.seseit.com> 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 : I'd quite like to avoid tokenising james from james@domain.com, because I : like the way PrefixQuery (when it works) matches james.dean@holywood.com well sure ... but if you say that becaues you want "." and "-" to be treaded specially you could write an Email EmailAnalyzer that produces the token stream: "james", "dean", "james.dean", "holywood.com", "james.dean@holywood.com" ... the real question is do you really want a search for "jam" to match "james.dean@holywood.com" while a search for "dean", "james dean" and "holywood.com" doesn't ? : -----Original Message----- : From: Chris Hostetter [mailto:hossman_lucene@fucit.org] : Sent: 15 June 2006 16:50 : To: java-user@lucene.apache.org : 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 : -Hoss --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org For additional commands, e-mail: java-user-help@lucene.apache.org