Could be normalized relative to the max score among the matching documents -
but I realize that this can only be done AFTER collecting the documents (as
the Hits class does currently). It could also be normalized to some
"absolute relevance score" that is comparable across queries, but there is
no
I figured out the answer to 2[a] - its because by default CustomScoreQuery
does weight normalization. To disable that, one should use
customQuery.setStrict(true). Once I do this, I get the original values that
I stored during the indexing process.
Help with the other two questions ([1] and [2]b)
A few questions on custom score queries:
[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-