: Another quick question on the score. If my custom Query is returning a score
: that can be any value, and this custom Query is being used together with
: other standard Query in a BooleanQuery. How do I ensure the value return by
: the custome Query doesnt 'overshadow' the values return by other
Chris, thanks again for your reply. Really appreciate your help.
Another quick question on the score. If my custom Query is returning a score
that can be any value, and this custom Query is being used together with
other standard Query in a BooleanQuery. How do I ensure the value return by
the cu
: (1) Should values returned by DocValues (return from ValueSource) must
: always betwen 1.0 and 0.0 ? How is this value affect the overall document
: scores, assuming there are others Query clauses as well that is perform on
: the document (on other fields).
The "values" returned by the various
Erick, thanks for your reply.
I have the LIA. But the sorting is not the solution I am looking for. As if
I sort, I will lose out the relevancy from searches of other fields. I want
the number proximity to be one in many of the fields that is searched. So
the "num" field will contribute to the ov
Sorry if this is a re-post, but I got an "undeliverable" error last time I
tried to post it, something about SPAM. The nerve of that filter!
I don't have my book handy, but you might want to check out "Lucene In
Action". There's an example of how to create an index of restaurants
Thanks Chis.
After spending half a day to "really" look into FunctionQuery (and related
classes), and re-reading about Weight and Scorer. I think I am beginning to
understand a bit. But more questions.
(1) Should values returned by DocValues (return from ValueSource) must
always betwen 1.0 and 0
: >From my searches, there seems to be a FunctionQuery in Solr that can do this
: type of query. But I am using pure Lucene, and trying to port Solr code over
: (to create my own version of FunctionQuery) looks too complicated because of
: code dependency on other Solr code such as ValueSource, et
