Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Mime-Version: 1.0 (Apple Message framework v728)
In-Reply-To: 
 <FBA9F803D33470489B9B4676A6B09F0B013F4BE8@mt-exch1.montreal.speechworks.com>
References: 
 <FBA9F803D33470489B9B4676A6B09F0B013F4BE8@mt-exch1.montreal.speechworks.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <B3C9259F-0C76-434A-BC38-B5E0B623D1B7@ehatchersolutions.com>
Content-Transfer-Encoding: 7bit
From: Erik Hatcher <erik@ehatchersolutions.com>
Subject: Re: PerFieldSimilarity
Date: Tue, 3 May 2005 19:40:21 -0400
To: java-user@lucene.apache.org


On May 3, 2005, at 5:57 PM, Robichaud, Jean-Philippe wrote:

> Hi Everyone,
>
> I've been searching the archive without success to answer this one:  
> is it
> possible to specify one similarity class per field, just like we  
> can do with
> an analyzer ?  I know I can change the similarity of the searcher,  
> but that
> restrict me to break some complex queries into different chunk and  
> sum the
> score "by hand" rather than having the fast internal implementation  
> do the
> job.  What I would really like is to have something like
> PerFieldAnalyzerWrapper but for similarity...  Is this possible ?

I'm interested in what your use case is in desiring this.  What  
factors would you vary per field?  The only factor that seems to make  
sense is lengthNorm which is computed at indexing time and does allow  
per-field tweaking.  A custom Similarity subclass could be used to  
affect the lengthNorm based on the field name parameter.

     Erik


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