: What is your query and "qf"?
FYI: these are both inlcuded in the original message (which was also
quoted in the reply below)
As jack points out, the differnece in score comes from thediffernece
in which fields are matched on.
Your high scoring example doc matches on *both* the
itemNo and itemNoExactMatchStr fields, but your low scoring example doc
matches only on the itemNo field. And you have a (relatively) huge boost
on the itemNoExactMatchStr field compared to itemNo.
These queries are fairly simple, so the explain output isn't very
complicated, and it's easy to see from the match -- but it may help to
prune out some of the small details, and just look at the top level
calculations...
: <str name="9030 ,0046,046">
: 12.014634 = (MATCH) max of:
: 0.20737723 = (MATCH) weight(itemNo:9030^0.9 in 2308681), product of:
: 12.014634 = (MATCH) fieldWeight(itemNoExactMatchStr:9030 in 2308681),
: </str>
...vs...
: <str name="90302 ,0046,046">
: 0.20737723 = (MATCH) max of:
: 0.20737723 = (MATCH) weight(itemNo:9030^0.9 in 1796597), product of:
: </str>
ou specified a huge boost on itemNoExactMatchStr, so the doc that matches
on that field is going to score a lot higher then the doc that only
matches on itemNo...
: <str name="qf">itemNoExactMatchStr^30 itemNo^.9 divProductTypeDesc^.8
: brand^.5</str>
-Hoss
