: document in the scoring formula, and I thought the CustomScoreQuery would be
: useful, but I am realizing that it may not be easy because the "relevance"
: score from Lucene has no absolute meaning. The relevance score could be 5 or
: 500 and there is no way for me gauge what that number means an
easaily weigh in the other factors
> : relative to it?
>
> normalized relative to what?
>
>
>
> -Hoss
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this m
: [1] I need to rank matches by some combination of keyword match, popularity
: and recency of the doc. I read the docs about CustomScoreQuery and seems to
: be a resonable fit. An alternate way of achieving my goals is to use a
: custom sort. What are the trade-offs between these two approaches?
g. So, any experiences related to this
issue is welcome.
--
View this message in context:
http://www.nabble.com/Question-on-custom-scoring-tf4264305.html#a12137476
Sent from the Lucene - Java Users mailing list archive at Nabble.com.
--
it difficult for me to weight the different
scores properly. Is there an easy way to get the normalized "text index"
score in customScore() API so I can easaily weigh in the other factors
relative to it?
Thanks a lot in advance,
Srinivas
--
View this message in context:
htt
