Hi,
We're interested in having access to the number of terms in the fields for
a document vs the pre-calculated lengthnorm at scoring time - we want
experiment with different lengthnorm functions so it seems like storing the
raw length and then doing the norm calculation at query time would work.
encodeNorm/decodeNorm methods
> of the similarity. The default uses a very lossy float->1byte
> transformation.
>
> Uwe
>
> -
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: u...@thetaphi.de
>
>
> > -Original Mess
mputeNorm(FieldInvertState state);
>
>
>
> On Thu, Jun 19, 2014 at 1:54 PM, Nalini Kartha
> wrote:
> > Thanks for the info!
> >
> > We're more interested in changing the lengthnorm function vs using
> > additional stats for scoring so option 2 seems lik
Jun 19, 2014 at 6:03 PM, Nalini Kartha
> wrote:
> > Sorry, I meant the encodeNormValue and decodeNormValue methods on the
> > TFIDFSimilarity class -
> >
> > public byte encodeNormValue(float f)
> > public float decodeNormValue(byte b)
> >
> >
> >
