Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Date: Wed, 17 Aug 2011 15:52:45 -0700 (PDT)
From: Chris Hostetter <hossman_lucene@fucit.org>
To: dev@lucene.apache.org
Subject: Re: Solr QueryResultKey hashCode() and equals()
In-Reply-To: 
 <CACvpS_XxiyHKHAryfAiOQcG3mXS2XOvN+gVxMzXKf=Gmd4=Jqw@mail.gmail.com>
Message-ID: <alpine.DEB.2.00.1108171544490.24129@bester>
References: 
 <CACvpS_XxiyHKHAryfAiOQcG3mXS2XOvN+gVxMzXKf=Gmd4=Jqw@mail.gmail.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


: with cache warming in Solr I found that the order of the Query objects
: within the filters list makes a difference to the equals() and hashCode()
: methods.
	...
: I found that it resulted in a cache miss for two queries that have the same
: results just because the filters had a different ordering. Am I missing
: something or is there an opportunity to improve the chance of matching cache
: entries?

I haven't dug into the code, but i suspect you are probably correct.  

Please open an issue drawing attention to this, but off the top of my head 
I'm not sure if there is a practical solution inside Solr -- Query classes 
aren't Comparable, so we can't do anythin simple like sort the List 
when executing the query or building the cache key.


-Hoss

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