lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erik Hatcher <e...@ehatchersolutions.com>
Subject Re: Similarity coord,lengthNorm
Date Mon, 07 Feb 2005 14:50:52 GMT

On Feb 7, 2005, at 8:53 AM, Michael Celona wrote:
> Would fixing the lengthNorm to 1 fix this problem?

Yes, it would eliminate the length of a field as a factor.

Your best bet is to set up a test harness where you can try out various 
tweaks to Similarity, but setting the length normalization factor to 
1.0 may be all you need to do, as the coord() takes care of the other 
factor you're after.

	Erik

>
> Michael
>
> -----Original Message-----
> From: Michael Celona [mailto:mcelona@criticalmention.com]
> Sent: Monday, February 07, 2005 8:48 AM
> To: Lucene Users List
> Subject: Similarity coord,lengthNorm
>
> I have varying length text fields which I am searching on.  I would 
> like
> relevancy to be dictated predominantly by the number of terms in my 
> query
> that match.  Right now I am seeing a high relevancy for a single word
> matching in a small document even though all the terms in my query 
> don't
> match.  Does, anyone have an example of a custom Similarity sub class 
> which
> overrides the coord and lengthNorm methods.
>
>
>
> Thanks..
>
> Michael
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: lucene-user-help@jakarta.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-user-help@jakarta.apache.org


Mime
View raw message