> 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
Hi Otis,
they are generally processed in docId order. The special case "out-of-order"
processing is only used for BooleanScorer1, in which the document IDs can be
reported to the Collector out-of-order (because BooleanScorer scores documents
in buckets). If you don’t allow out-of-order scoring,
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
Use CustomScoreQuery. The external values can be looked up in the
CustomScoreProvider. The CSQ wraps the original Lucene Query and can multiply
in extra factors.
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
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
