lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hany Azzam" <>
Subject Re: How disabling norms on a field effects other fields
Date Tue, 06 Mar 2012 22:56:30 GMT
i.e. Field length :)

A trivial question maybe: if one uses these flags does that mean they don't need to override
the computeNorm method as shown in Simon's article on seachworkings? I am referring to the
case when one doesn't want to use norms.

-----Original Message-----
From: Paul Taylor <>
Date: Tue, 06 Mar 2012 21:48:17 
To: <>
Subject: Re: How disabling norms on a field effects other fields

On 06/03/2012 21:44, Paul Taylor wrote:
> I have a number of fields that either only ever have a term frequency 
> of 1 or I don't want them to be disavantaged if they do have a greater 
> term frequency, and I never boost the field so I disable norms for 
> these fields with Field.Index.ANALYZED_NO_NORM or 
> But  if I'm searching using two fields
> i.e
> a:term1 OR b:term2
> and A has norms enabled and B doesn't, doesnt't that mean  that 
> documents that match B are more likely to score better than documents 
> that match A because when the score for a document matching just A 
> will end up with a lower score in the weight = tf * idf * fieldnorm 
> calculation.
> Thats not what I wanted,  I just wanted a document matching on field B 
> which contained three terms to score as well as a match on a document 
> field B with one term
> Have I understood this right, if so what the solution ?
Sorry , quick correction when I say Term Frequency I don't mean tf (i.e 
matching terms), I just mean Number of Terms in the Field


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

View raw message