lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <>
Subject [jira] Commented: (LUCENE-1896) Modify confusing javadoc for queryNorm
Date Tue, 08 Sep 2009 21:43:57 GMT


Hoss Man commented on LUCENE-1896:

as i mentioned in the linked thread, the biggest advantage i know of for queryNorm is that
it is a reduction factor applied to the constituent parts of a complex score prior to multiplication
-- so it helps prevent loss of information due to floating point accuracy that could arrise

but then again: that'swhat the *default* queryNorm does ... an alternate queryNorm could do
something (like be a no-op)

Since the target audience of the Similarity javadocs are mainly people who are interested
in customizing the scoring, perhaps it should be something like...

The queryNorm is a uniform normalization factor computed from the sumOfSquareWeights for the
query which is then applied to each of the clauses of the query.  In some cases this can be
useful for attempting to keep scores from simple queries semi-comparable.  The Default implementation

> Modify confusing javadoc for queryNorm
> --------------------------------------
>                 Key: LUCENE-1896
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Javadocs
>            Reporter: Jiri Kuhn
>            Priority: Minor
>             Fix For: 2.9
> See
> The javadoc confuses me as well.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message