Return-Path: Delivered-To: apmail-lucene-java-dev-archive@www.apache.org Received: (qmail 4710 invoked from network); 17 Oct 2006 19:42:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 17 Oct 2006 19:42:02 -0000 Received: (qmail 61040 invoked by uid 500); 17 Oct 2006 19:41:59 -0000 Delivered-To: apmail-lucene-java-dev-archive@lucene.apache.org Received: (qmail 61003 invoked by uid 500); 17 Oct 2006 19:41:59 -0000 Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-dev@lucene.apache.org Delivered-To: mailing list java-dev@lucene.apache.org Received: (qmail 60992 invoked by uid 99); 17 Oct 2006 19:41:59 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Oct 2006 12:41:59 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [64.34.172.19] (HELO ohana.manawiz.com) (64.34.172.19) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Oct 2006 12:41:57 -0700 Received: from [192.168.1.47] ([::ffff:72.234.69.162]) (AUTH: LOGIN chuck, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by ohana.manawiz.com with esmtp; Tue, 17 Oct 2006 19:41:35 +0000 id 0070C1BB.453531EF.00006578 Message-ID: <453531ED.9080302@manawiz.com> Date: Tue, 17 Oct 2006 09:41:33 -1000 From: Chuck Williams Organization: Manawiz User-Agent: Thunderbird 1.5.0.7 (X11/20060927) MIME-Version: 1.0 To: java-dev@lucene.apache.org Subject: Re: Include BM25 in Lucene? References: <4534D017.7050100@america.net> In-Reply-To: <4534D017.7050100@america.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Vic Bancroft wrote on 10/17/2006 02:44 AM: > In some of my group's usage of lucene over large document collections, > we have split the documents across several machines. This has lead to > a concern of whether the inverse document frequency was appropriate, > since the score seems to be dependant on the partioning of documents > over indexing hosts. We have not formulated an experiment to > determine if it seriously effects our results, though it has been > discussed. What version of Lucene are you using? Are you using ParallelMultiSearcher to manage the distributed indexes or have you implemented your own mechanism? There was a bug a couple years ago, in the 1.4.3 version as I recall, where ParallelMultiSearcher was not computing df's appropriately, but that has been fixed for a long time now. The df's are the sum of the df's from each distributed index and thus are independent of the partitioning. Chuck --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org For additional commands, e-mail: java-dev-help@lucene.apache.org