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 38BC810DA6 for ; Tue, 27 Aug 2013 01:15:47 +0000 (UTC) Received: (qmail 34539 invoked by uid 500); 27 Aug 2013 01:15:45 -0000 Delivered-To: apmail-lucene-java-user-archive@lucene.apache.org Received: (qmail 34492 invoked by uid 500); 27 Aug 2013 01:15:45 -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 34484 invoked by uid 99); 27 Aug 2013 01:15:45 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Aug 2013 01:15:45 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of msokolov@safaribooksonline.com designates 209.85.216.50 as permitted sender) Received: from [209.85.216.50] (HELO mail-qa0-f50.google.com) (209.85.216.50) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Aug 2013 01:15:38 +0000 Received: by mail-qa0-f50.google.com with SMTP id o13so2048335qaj.2 for ; Mon, 26 Aug 2013 18:15:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=safaribooksonline.com; s=google; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=b12S8ynzodcGR2jMWrCqRdT+mDZ+MbxvMP94GcYXx7k=; b=KFLWVOVYLdBAKVbULu4Msu9OTT9NcwKjiyJbZKhd8i+lalcMU/mvP0///5tV8eOzd8 E13zPydznKuZCqVRGTFLp7Qe5tSLiNzlSvoF0GfNRZcISHrxsZBh8IN7HI1Vaw0sKh9t VtOKB52G+k3lyV4PggtxDNhVYCDodTqR5fhf4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=b12S8ynzodcGR2jMWrCqRdT+mDZ+MbxvMP94GcYXx7k=; b=lil6NnalUcf03T+KKwtFzwZ9QRc8ZjhiqJBy7NWx5V/XKl3LgakuQh6ChooewQCt5O NL44VCmRxy6sZOVe+FEcrfCYL0uzUeZZ7n92fNAyN9B323t1Kasml1H4+3LSc7WrO7S1 wpoAxSM9uC+y7BnBYmBcf0+kvCwgecZA1QnN/s8f3SPzn6Zfuruwu8ELBk0GHOIzTGEH R35ntis5BGWgPOQmzwksbYKitML6jsj4OwiKlNYX2c7Sd5erJSmKBp1uxswEgtmbK5EQ i7dBRPhvObNwtIhpD+EvFstPeWuAeQmPdf13tdiTyeO2kI9CJ8/YJ1a8UVEdD9mXq/su p4gg== X-Gm-Message-State: ALoCoQnOPRQLGTXDlZ+IDOy+wvGSrMioycc5RlCSaotfeMM7UdueACudEWoGC+/Btsur8NitL5Yo X-Received: by 10.224.126.67 with SMTP id b3mr14373qas.95.1377566117386; Mon, 26 Aug 2013 18:15:17 -0700 (PDT) Received: from [192.168.1.7] (pool-173-76-231-7.bstnma.fios.verizon.net. [173.76.231.7]) by mx.google.com with ESMTPSA id s9sm24525060qev.6.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 26 Aug 2013 18:15:16 -0700 (PDT) Message-ID: <521BFDA4.20002@safaribooksonline.com> Date: Mon, 26 Aug 2013 21:15:16 -0400 From: Michael Sokolov User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: java-user@lucene.apache.org Subject: Re: Document boosting and native ordering of results References: <52138CEA.9010701@loot.co.za> <521B8486.4020802@loot.co.za> <033101cea282$eef78490$cce68db0$@thetaphi.de> In-Reply-To: <033101cea282$eef78490$cce68db0$@thetaphi.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org I had been planning something similar to what Michael was used to: creating a regular numeric field (call it "weight", say) with a rank value, applying a field boost to that field that is equal to the rank value, and then querying with weight:[* TO *] as a term, thinking that would end up bringing in the rank to the scoring calculation. Is that not going to work? Is it necessary or better to use DocValues with a FunctionQuery? Thanks Mike On 8/26/13 1:37 PM, Uwe Schindler wrote: > Hi, > > This is still possible (in reality it was broken in Lucene version prior 4.0 if you refer to Document.setBoost() -> see changelog/MIGRATE.txt): You have to add an additional DocValues field (a long or double numeric) and use a FunctionQuery / CustomScoreQuery to modify the score based on this value. > > Uwe > > ----- > Uwe Schindler > H.-H.-Meier-Allee 63, D-28213 Bremen > http://www.thetaphi.de > eMail: uwe@thetaphi.de > > >> -----Original Message----- >> From: Michael van Rooyen [mailto:michael@loot.co.za] >> Sent: Monday, August 26, 2013 6:39 PM >> To: java-user@lucene.apache.org >> Subject: Re: Document boosting and native ordering of results >> >> Not sure if there are any thoughts on this. >> >> It definitely makes sense to assign a rank to each document in the index, so >> that all else being equal, documents are returned in order of rank. This is >> exactly what the page rank is in Google's index, and Google would be lost >> without it. This used to be possible in old versions of Lucene, but no longer. >> Should this be posted as a feature request to the developers? >> >> Thanks, >> Michael. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org >> For additional commands, e-mail: java-user-help@lucene.apache.org > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org > For additional commands, e-mail: java-user-help@lucene.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org For additional commands, e-mail: java-user-help@lucene.apache.org