Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@lucene.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Date: Wed, 24 May 2006 14:42:28 -0700 (PDT)
From: Chris Hostetter <hossman_lucene@fucit.org>
To: java-dev@lucene.apache.org
Subject: Re: SweetSpotSimiliarity
In-Reply-To: <9B43CB81-30F8-47A2-998C-077FC0FA994B@rectangular.com>
Message-ID: <Pine.LNX.4.58.0605241437110.16609@hal.rescomp.berkeley.edu>
References: <9807227.1148432130297.JavaMail.jira@brutus>
 <F9F270C4-FA1E-460F-A54F-E2E56AAD0286@rectangular.com>
 <Pine.LNX.4.58.0605232225480.5337@hal.rescomp.berkeley.edu>
 <44749BF8.2090601@apache.org>
 <Pine.LNX.4.58.0605241120410.8452@hal.rescomp.berkeley.edu>
 <4474A6F6.7010102@apache.org>
 <2FF50110-74F5-4FE7-A85D-EAD815220FDF@rectangular.com>
 <4474B8DB.3070303@apache.org>
 <9B43CB81-30F8-47A2-998C-077FC0FA994B@rectangular.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


: into Scorers, I feel like I have to go spelunk all of them to make
: sure that no Query ever propagates its Similarity instance to a child
: in such a way.  Making the broad statement that all instances of

i don't think there is any situation where a Query passes it's similarity
down into any subqueries it may have -- there isn't even a mechanism for
it other then to wrap each subquery in some sort of delegating proxy class
at rewrite time.

it would be possibe to write a query class A which would rewrite to an
anonymous subclass of B with getSimilarity overrien to use A's similarity,
but that would be a lot of work, and i don't think any Query goes to that
trouble.


-Hoss


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