Re: disable field length normalization on specific fields?

2016-03-28 Thread Chris Hostetter
e currently using -- look for usages of FieldInvertState.getLength() and remove/replace that with a fixed value. : Date: Wed, 9 Mar 2016 13:23:16 -0500 : From: Matt Savona : Reply-To: java-user@lucene.apache.org : To: java-user@lucene.apache.org : Subject: disable field length normalization on

disable field length normalization on specific fields?

2016-03-09 Thread Matt Savona
Hi all, I am trying to understand if the following is possible: I would like to have several fields in my index which are boosted at index time. Because they are to be boosted at index time, their field type requires omitNorms(false). However, I do not want field length normalization to affect

Re: Field length normalization

2005-10-07 Thread Erik Hatcher
On Oct 7, 2005, at 11:17 AM, Sameer Shisodia wrote: thnx Erik. Is returning a default constant the answer i'm looking for ? Perhaps. Try returning 1.0f - experimentation is always warranted when playing with scoring tweaks. Have a look at IndexSearcher.explain() to see why documents sco

Re: Field length normalization

2005-10-07 Thread Sameer Shisodia
thnx Erik. Is returning a default constant the answer i'm looking for ? btw, the book is kewl :) sameer On 10/7/05, Erik Hatcher <[EMAIL PROTECTED]> wrote: > > > On Oct 7, 2005, at 4:14 AM, Sameer Shisodia wrote: > > > Hi, > > Have started using Lucene recently so this might be a oft repeated > >

Re: Field length normalization

2005-10-07 Thread Erik Hatcher
On Oct 7, 2005, at 4:14 AM, Sameer Shisodia wrote: Hi, Have started using Lucene recently so this might be a oft repeated qn (Do point me to archives if any). I'm storing multiple values of a field as a comma separated string during indexing. Obviously, some docs have more values and some only

Field length normalization

2005-10-07 Thread Sameer Shisodia
Hi, Have started using Lucene recently so this might be a oft repeated qn (Do point me to archives if any). I'm storing multiple values of a field as a comma separated string during indexing. Obviously, some docs have more values and some only one and so hits against those with multiple values for