Return-Path: Delivered-To: apmail-lucene-java-user-archive@www.apache.org Received: (qmail 22164 invoked from network); 17 Mar 2009 23:19:10 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 17 Mar 2009 23:19:10 -0000 Received: (qmail 21231 invoked by uid 500); 17 Mar 2009 23:19:02 -0000 Delivered-To: apmail-lucene-java-user-archive@lucene.apache.org Received: (qmail 21206 invoked by uid 500); 17 Mar 2009 23:19:02 -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 21195 invoked by uid 99); 17 Mar 2009 23:19:02 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Mar 2009 16:19:02 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [208.69.42.181] (HELO radix.cryptio.net) (208.69.42.181) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Mar 2009 23:18:55 +0000 Received: by radix.cryptio.net (Postfix, from userid 1007) id 2131B71C2F7; Tue, 17 Mar 2009 16:18:35 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by radix.cryptio.net (Postfix) with ESMTP id 1EDC071C2F6 for ; Tue, 17 Mar 2009 16:18:35 -0700 (PDT) Date: Tue, 17 Mar 2009 16:18:35 -0700 (PDT) From: Chris Hostetter To: java-user@lucene.apache.org Subject: Re: sloppyFreq question In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Checked: Checked by ClamAV on apache.org : > I suppose SpanTermQuery could override the weight/scorer methods so that : > it behaved more like a TermQuery if it was executed directly ... but : > that's really not what it's intended for. : : This is currently the only way to boost a term via payloads. : BoostingTermQuery extends SpanTermQuery. probably because it was the easiest way to get at the payload ... another reason to cahnge SpanTermQuery's weight i guess. : > if you're talking about a SpanNearQuery of "the quick brown fox" vs a : > SpanNearQuery of "brown fox" -- both against some doc like "hey look, the : > quick brown fox jumped very high" -- then sure, that doc might produce a : > lower score for the first query then it does for the second query ... but : > scores from differnet queries aren't comparable. : : Yes, this is the case I meant. To the casual observer, they both appear to : be "exact matches' with respect to term frequency. However, I realize that : the first query would score higher than the 2nd if all 4 terms were indexed : at the same position. I guess this is part of the point you're making about : spans. Would a plain PhraseQuery behave this way, too? i think you're missing my point -- it's not specific to spans: it doesn't mean *anything* to say "the first query would score higher then the 2nd" because scores aren't comparable between queries. (unless you really go out of your way to make them comparable by customizing Similarity, and ensuring that they have hte exact same structure -- a SpanNearQuery containing 5 SpanTermQueries doesn't have the same structure as a SpanNearQuery containing two SpanTermQueries) -Hoss --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org For additional commands, e-mail: java-user-help@lucene.apache.org