fieldNorm is the combination of length of the field with index and query
time boosts.
1. lengthNorm = measure of the importance of a term according to the
total number of terms in the field
1. Implementation: 1/sqrt(numTerms)
2. Implication: a term matched in fields with less terms have a
higher score
3. Rationale: a term in a field with less terms is more important
than one with more
2. boost (index) = boost of the field at index-time
1. Index time boost specified. The fieldNorm value in the score
would include the same.
3. boost (query) = boost of the field at query-time
bf is the query time boost for a field and should affect fieldNorm value.
queryNorm is just a normalization factor so that queries can be compared and
will differ based on query and results
1. queryNorm is not related to the relevance of the document, but rather
tries to make scores between different queries comparable. It is
implemented
as 1/sqrt(sumOfSquaredWeights)
You should not be bothered about queryNorm, as for a query it will have the
same value for all the results.
Regards,
Jayendra
On Tue, Nov 30, 2010 at 9:37 AM, Gastone Penzo <[email protected]>wrote:
> Hello,
> someone can explain the difference between queryNorm and FieldNorm in
> debugQuery??
> why if i push one bf boost up, the queryNorm goes down??
> i made some modifies..before the situation was different. why??
> thanx
>
> --
> Gastone Penzo
>
