Return-Path: Delivered-To: apmail-lucene-java-user-archive@www.apache.org Received: (qmail 19903 invoked from network); 7 Mar 2006 07:02:06 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 7 Mar 2006 07:02:06 -0000 Received: (qmail 27941 invoked by uid 500); 7 Mar 2006 07:01:55 -0000 Delivered-To: apmail-lucene-java-user-archive@lucene.apache.org Received: (qmail 27852 invoked by uid 500); 7 Mar 2006 07:01:55 -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 27823 invoked by uid 99); 7 Mar 2006 07:01:54 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Mar 2006 23:01:54 -0800 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; Mon, 06 Mar 2006 23:01:53 -0800 Received: by rescomp.berkeley.edu (Postfix, from userid 1007) id EA2C95B76C; Mon, 6 Mar 2006 23:01:31 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by rescomp.berkeley.edu (Postfix) with ESMTP id E3CB97F403 for ; Mon, 6 Mar 2006 23:01:31 -0800 (PST) Date: Mon, 6 Mar 2006 23:01:31 -0800 (PST) From: Chris Hostetter To: java-user@lucene.apache.org Subject: Re: Help interpreting explanation In-Reply-To: <440D1200.1050402@gmail.com> Message-ID: References: <440731D5.1050101@gmail.com> <5a2e14740603021836m2a700055x2a7462160ddfda9@mail.gmail.com> <440864B4.1020105@gmail.com> <44086B56.4040509@gmail.com> <4408700F.8010502@gmail.com> <4408EC35.7020909@gmail.com> <440B3188.20904@gmail.com> <440B3AED.6010407@isb-sib.ch> <440BCE8A.4090904@gmail.com> <440C2342.4000809@gmail.com> <440D1200.1050402@gmail.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 : on using Lucene but info for the internal workings of Lucene is hard to : come by. As with many OS code bases: the code is the documentation. : 1) I'm using the default QueryParser to parse and return a query so it's : a Boolean-OR query. So does this mean it uses the DisjunctionSumScorer : or something? I honestly don't understand all the ways the different Scorers are used for BooleanQueries. The thing to keep in mind is that they are all optimizations that get choosen based on wether some/all clauses are required, wether any clauses are prohibited, etc... If you understand what the basic BooleanScorer does, then you understand what all of the other Scorers do -- they just go about it in slightly different ways. : 2) Just wondering looking at the API for BooleanQuery i saw this: "Using : setMinimumNumberShouldMatch will force the use of BooleanWeight2, : regardless of wether setUseScorer14(true) has been called." : What is the method setUseScorer14 about? Hmmm... i guess it's not really documented is it? setUseScorer14(true) is just a way to force the old lucene 1.4.x style Boolean Scoring. I don't really know why that code was left in, or why you might want to use it. -Hoss --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org For additional commands, e-mail: java-user-help@lucene.apache.org