Return-Path: Delivered-To: apmail-lucene-java-user-archive@www.apache.org Received: (qmail 12630 invoked from network); 18 Dec 2009 17:41:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 18 Dec 2009 17:41:09 -0000 Received: (qmail 73711 invoked by uid 500); 18 Dec 2009 17:41:07 -0000 Delivered-To: apmail-lucene-java-user-archive@lucene.apache.org Received: (qmail 73644 invoked by uid 500); 18 Dec 2009 17:41:07 -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 73634 invoked by uid 99); 18 Dec 2009 17:41:07 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Dec 2009 17:41:07 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of prabin.meitei@gmail.com designates 209.85.160.46 as permitted sender) Received: from [209.85.160.46] (HELO mail-pw0-f46.google.com) (209.85.160.46) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Dec 2009 17:40:59 +0000 Received: by pwj16 with SMTP id 16so2394195pwj.5 for ; Fri, 18 Dec 2009 09:40:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=O81oCDOLj9M8fjMOCGTV2m+Dvc1iDk9kkP1rFdhFhhM=; b=M+yvYlCd7Zveij0IWCVZeiPHvmUZSAuTeCR8JoDvQwAVJ83KO/lZXoVkezBZqF+ZTz jJLorE4WLZLpmljvWRNwPOzPWJ89JqL4eaJeROmFEzVZnWtCM9Dd36yUUafDwporf0vR KSi9wqAF22ZIxKtazg0/Y+VOkKjzway+cWdh8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=KrOjVBc7JXzvCxLwyGfvwFRmx9pPSAYseW4dw6VtrLT3NoTJFQ3BXW7vOgPQ1i2kWi ld9N8dSEDnNomz3dS4J0ojZKneNOxRLh1MRUQi6E4ZNzftwnkH6NjLOa57VPDe4kZSBp OdgXMidIvnRGaSas7G8ornVtgDjExWswVifxg= MIME-Version: 1.0 Received: by 10.114.236.22 with SMTP id j22mr2730305wah.217.1261158038222; Fri, 18 Dec 2009 09:40:38 -0800 (PST) Date: Fri, 18 Dec 2009 23:10:38 +0530 Message-ID: <295da8fe0912180940j14fe0772y83050ccbc6636863@mail.gmail.com> Subject: document with different index time boost returns same score From: prabin meitei To: java-user@lucene.apache.org Content-Type: multipart/alternative; boundary=0016e64b96e2dfba77047b043ce0 X-Virus-Checked: Checked by ClamAV on apache.org --0016e64b96e2dfba77047b043ce0 Content-Type: text/plain; charset=ISO-8859-1 Hi, I have an index in which documents are inserted with different boost during indexing. eg. doc1 has boost 5.64 doc2 has boost 5.25 doc3 has boost 5.10 doc4 has boost 4.8 doc5 has boost 4.4 doc6 has boost 4.0 and so on... some documents even having boost only 1.0 when i search the index for a term which occur only once in these documents i expected that the final scores of the search hit will differ according to the document boost set during indexing. But surprisingly i found that doc1, doc2 and doc3 have same score (even the raw score) and doc4 and doc5 have same score. I even tried changing index time boost to 564, 525, 510 .. and so on for doc1, doc2 doc3 and so on... but it still returned same result. Can anyone explain what is happening? why the scores are same even when the index time boost was different. Is there any other way to implement my expected result. any help will be highly appreciated. Prabin --0016e64b96e2dfba77047b043ce0--