Return-Path: Delivered-To: apmail-lucene-java-user-archive@www.apache.org Received: (qmail 36372 invoked from network); 17 Aug 2007 06:50:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 17 Aug 2007 06:50:51 -0000 Received: (qmail 85996 invoked by uid 500); 17 Aug 2007 06:50:43 -0000 Delivered-To: apmail-lucene-java-user-archive@lucene.apache.org Received: (qmail 85862 invoked by uid 500); 17 Aug 2007 06:50:43 -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 85851 invoked by uid 99); 17 Aug 2007 06:50:43 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Aug 2007 23:50:43 -0700 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [169.229.70.150] (HELO rescomp.berkeley.edu) (169.229.70.150) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Aug 2007 06:51:02 +0000 Received: by rescomp.berkeley.edu (Postfix, from userid 1007) id B14AD95A11; Thu, 16 Aug 2007 23:50:19 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by rescomp.berkeley.edu (Postfix) with ESMTP id 9A96623702 for ; Thu, 16 Aug 2007 23:50:19 -0700 (PDT) Date: Thu, 16 Aug 2007 23:50:18 -0700 (PDT) From: Chris Hostetter To: java-user@lucene.apache.org Subject: Re: Question on custom scoring In-Reply-To: <12154865.post@talk.nabble.com> Message-ID: References: <12136012.post@talk.nabble.com> <12154865.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Checked: Checked by ClamAV on apache.org : document in the scoring formula, and I thought the CustomScoreQuery would be : useful, but I am realizing that it may not be easy because the "relevance" : score from Lucene has no absolute meaning. The relevance score could be 5 or : 500 and there is no way for me gauge what that number means and how much I : should weigh he "popularity" value relative to it when computing the custom it's definitely tricky, and not something that can be decided universally regardless of your data (or query structure) -- like all "fuzzy" logic you have to try lots of different use cases and find something that works well. And yes, you have to re-evaluate your choices over time sa you index changes. -Hoss --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org For additional commands, e-mail: java-user-help@lucene.apache.org