The DocSet isn't part of the cache key. The key is usually just a simple string
(e.g. companyId). They just return a DocSet. I think the user caches are fine.
This DocSet is then used as a filter for the actual query. I believe it is this
step that is slow.
However, I am guessing that the solution is still to have the user caches
return a Query object so that I can supply a List<Query> to SolrIndexSearcher,
causing it to use the QueryResultsCache. Correct?
----- Original Message ----
From: Yonik Seeley <[EMAIL PROTECTED]>
To: solr-user@lucene.apache.org
Sent: Thursday, August 14, 2008 1:41:50 PM
Subject: Re: QueryResultsCache and DocSet filter
On Thu, Aug 14, 2008 at 3:15 PM, Kevin Osborn <[EMAIL PROTECTED]> wrote:
> The problem here is that the calls in SolrIndexSearcher don't appear to use
> the QueryResultsCache if the filer is a DocSet rather than a List<Query>.
Right... using a DocSet as part of the cache key would be pretty slow
(key comparisons) and more memory intensive.
> Is it recomended to re-work the caches to return Query objects and use that
> as my filterList?
Yes, that should work.
-Yonik
