> Hi Otis,
>
> It depends on the Scorer implementation. The default iterates through
> matching documents by calling nextDoc(), which just moves along the
> postings lists in-order, but you could roll your own. You're pretty
> constrained
> by the fact that the low-level DocIdSetIterators only
Hi Otis,
It depends on the Scorer implementation. The default iterates through matching
documents by calling nextDoc(), which just moves along the postings lists
in-order, but you could roll your own. You're pretty constrained by the fact
that the low-level DocIdSetIterators only move forward
56 AM
> To: java-user@lucene.apache.org
> Subject: Document scoring order?
>
> Hi,
>
> When Lucene scores matching documents, what is the order in which
> documents are processed/scored and can that be changed? I'm guessing it
> scores matches in whichever order they
Hi,
When Lucene scores matching documents, what is the order in which
documents are processed/scored and can that be changed? I'm guessing
it scores matches in whichever order they are stored in the index/on
disk, which means by increasing docIDs?
I do see some out of order scoring is possible..
I modify TopDocsCollector and collect some to-score value store in index to
an array and then calculate them with similar score,return final score to
sort the docs.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Document-scoring-tp4018582p4018962.html
Sent from the Lucene
age-
> From: parnab kumar [mailto:parnab.2...@gmail.com]
> Sent: Tuesday, November 06, 2012 7:53 PM
> To: java-user@lucene.apache.org
> Subject: Document scoring
>
> Hi All,
>
> I am using lucene 3.x . I need some flexibility for document scoring . For
> instance, aft
Try TopDocs. You can use getMaxScore and divide
Best
Erick
On Thu, Mar 20, 2008 at 11:12 AM, Cam Bazz <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I am querying an index by using custom boost factors for each field.
> Usually
> a query looks like:
>
> fieldA:"term1"^0.2 fieldB:"term2"^4
>
> when
Hello,
I am querying an index by using custom boost factors for each field. Usually
a query looks like:
fieldA:"term1"^0.2 fieldB:"term2"^4
when I get scores from HitCollector, they are not necessarily between 0 and
1.
How can I normalize these scores?
Best.
-C.A.
