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: [email protected]
-----Original Message-----
From: Michael van Rooyen [mailto:[email protected]]
Sent: Monday, August 26, 2013 6:39 PM
To: [email protected]
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: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
