Return-Path: X-Original-To: apmail-lucene-java-user-archive@www.apache.org Delivered-To: apmail-lucene-java-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9E3302916 for ; Thu, 5 May 2011 07:18:21 +0000 (UTC) Received: (qmail 93232 invoked by uid 500); 5 May 2011 07:18:17 -0000 Delivered-To: apmail-lucene-java-user-archive@lucene.apache.org Received: (qmail 93089 invoked by uid 500); 5 May 2011 07:18:11 -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 92703 invoked by uid 99); 5 May 2011 07:18:07 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 May 2011 07:18:07 +0000 X-ASF-Spam-Status: No, hits=2.5 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,FREEMAIL_REPLYTO_END_DIGIT,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of paul_t100@fastmail.fm designates 66.111.4.26 as permitted sender) Received: from [66.111.4.26] (HELO out2.smtp.messagingengine.com) (66.111.4.26) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 May 2011 07:18:00 +0000 Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id 8A474209A9; Thu, 5 May 2011 03:17:39 -0400 (EDT) Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute3.internal (MEProxy); Thu, 05 May 2011 03:17:39 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=message-id:date:from:reply-to:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; s=smtpout; bh=9PBPPuzCNxrjUjvPU2UrkDGYRJs=; b=Q7sHifOY+IOZntHGarPgyEpVUt4P2ur6mQkBtB7uS7srHoRGsf8sI9IKtexI68swV1Gp5KVTY2KPVqyRmcgoifZ5YZAoQfCNFEnc17EyYe0VmhMfjUySjzquKwJR2kGBUfJZ9sSP6o61HL2RzxBObJzZORlBaB/d8qOzPYfytxI= X-Sasl-enc: nuVJYk692nYthoIhNTD/qYHod7L0jeJ1iLq8VUPulhul 1304579859 Received: from [192.168.1.65] (unknown [217.155.98.246]) by mail.messagingengine.com (Postfix) with ESMTPSA id F40EF4429D2; Thu, 5 May 2011 03:17:38 -0400 (EDT) Message-ID: <4DC24F12.30903@fastmail.fm> Date: Thu, 05 May 2011 08:17:38 +0100 From: Paul Taylor Reply-To: paul_t100@fastmail.fm User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 To: java-user@lucene.apache.org CC: Chris Hostetter Subject: Re: Anyway to not bother scoring less good matches ? References: <4DBFEBCD.9090504@fastmail.fm> <89331.21012.qm@web121716.mail.ne1.yahoo.com> <4DC13DDD.6010905@fastmail.fm> <4DC147C1.7020206@fastmail.fm> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On 05/05/2011 00:24, Chris Hostetter wrote: > : Well I did extend QuerParser, and the method is being called but rather > : disappointingly it had no noticeablke effect on how long queries took. I > : really thought by reducing the number of matches the corresponding scoring > : phase would be quicker. > > "matching" and "scoring" go hand in hand ... the Searcher iterates over > all docs to determine if they match the Query (i'm being grossly simple, > in truth many docs can be skipped wholesale during this iteration because > of conjunctions) and when a matching document is found, it's score is > computed to determine if it's high enough to be included in the results > (ie: is it's score higher then the lowest scoring document already > collected) > > The botomline: lucene doesn't know that something is a "less good match" > until it scores it ... the score is what determines how good it is. > > > -Hoss > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org > For additional commands, e-mail: java-user-help@lucene.apache.org > > But doesnt setting setMinimumNumberShouldMatch(3) cause the search to decide that a document that only matches two terms does not match the query in the first place, therefore not need scoring ? Paul --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org For additional commands, e-mail: java-user-help@lucene.apache.org