Return-Path: Delivered-To: apmail-lucene-java-user-archive@www.apache.org Received: (qmail 52361 invoked from network); 13 Oct 2007 06:54:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 13 Oct 2007 06:54:27 -0000 Received: (qmail 88041 invoked by uid 500); 13 Oct 2007 06:54:09 -0000 Delivered-To: apmail-lucene-java-user-archive@lucene.apache.org Received: (qmail 88016 invoked by uid 500); 13 Oct 2007 06:54:09 -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 87994 invoked by uid 99); 13 Oct 2007 06:54:09 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Oct 2007 23:54:09 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lukas.vlcek@gmail.com designates 209.85.198.187 as permitted sender) Received: from [209.85.198.187] (HELO rv-out-0910.google.com) (209.85.198.187) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 13 Oct 2007 06:54:11 +0000 Received: by rv-out-0910.google.com with SMTP id k20so844705rvb for ; Fri, 12 Oct 2007 23:53:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; bh=lj7oUZP3t4PWWhtiCQvoyPdBfKg8khx6u1TnlWmjKM8=; b=mLIUmq1G1Doo4bPfWIK94kOBBVtoPtycPMTEs8MlOtyaEb1hKH7deVwDG9NVkdIrFum6gGlQxInN1coRJ3TZhRa2PAYtqJwjyVKsdKAE7nVf12CNXuoRxl2ND21T3EkRlYpjbXB8LRbeebML7wckDbedNUZfkLIERvzWslNacBs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=Fefi5FzRSROAU+bjgauQWINu6kyqi2wv8h6qlOhyyXyMaLMZixxUKEex17d8OuFEdziTbfH24HnGKLE9MgKWi9PLbj4bJdsEG/l3n1uyju9pX1AcuGztPo9TdxUigugbGywska7gI+atOOYNGgPHXUp7k4Dadvh3+YBWdxHu2U0= Received: by 10.141.185.3 with SMTP id m3mr1903597rvp.1192258427995; Fri, 12 Oct 2007 23:53:47 -0700 (PDT) Received: by 10.141.210.7 with HTTP; Fri, 12 Oct 2007 23:53:47 -0700 (PDT) Message-ID: <52c3ddca0710122353u36735e0bobd993c27552538b7@mail.gmail.com> Date: Sat, 13 Oct 2007 08:53:47 +0200 From: "Lukas Vlcek" To: java-user@lucene.apache.org Subject: Customized search with Lucene? MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_36115_28885873.1192258428002" X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_36115_28885873.1192258428002 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi, I am looking for an easy (~preferred) way of implementing customized search with Lucene. What I mean by this is changing order of returned hits according to user profile. In simple words I would like to be able to tweak order of documents in Hits collection before it is presented to the client. Example: if user A issues a query "lucene" then he/she tends to click the third returned link (document #123). I would like to "boost" document #123 for this user so the next time he/she issues the query "lucene" again the hit for the document #123 will be in the first or second position (providing that the index hasn't been modified). Looking at the Searchableinterface it does not seem it supports this kind of flexibility. I don't want to use filterof sort(they are not appropriate for my goal). Custom scoringseems to be the only option left. At the first glance it seems quite complex; moreover, I am not sure it really allows me to achieve my goal, but if there is no other way then I have to try it... Any suggestions? Regards, Lukas -- http://blog.lukas-vlcek.com/ ------=_Part_36115_28885873.1192258428002--