RE: Query optimisation - multiple filter caches?

2007-08-22 Thread Jonathan Woods 
I understand - thanks, Yonik.

I notice that LuceneQueryOptimizer is still used in
SolrIndexSearcher.search(Query, Filter, Sort) - is the idea then that this
method is deprecated, or that the config parameter
query/boolTofilterOptimizer is no longer to be used?  As for the other
search() methods, they just delegate directly to
org.apache.lucene.search.IndexSearcher, so no use of caches there.

Jon

 -Original Message-
 From: Yonik Seeley [mailto:[EMAIL PROTECTED] 
 Sent: 16 August 2007 01:40
 To: solr-user@lucene.apache.org
 Subject: Re: Query optimisation - multiple filter caches?
 
 On 8/15/07, Jonathan Woods [EMAIL PROTECTED] wrote:
  I'm trying to understand how best to integrate directly with Solr 
  (Java-to-Java in the same JVM) to make the most of its query 
  optimisation - chiefly, its caching of queries which merely filter 
  rather than rank results.
 
  I notice that SolrIndexSearcher maintains a filter cache 
 and so does 
  LuceneQueryOptimiser.  Shouldn't they be contributing to/using the 
  same cache, or are they used for different things?
 
 LuceneQueryOptimiser is no longer used since one can directly 
 specify filters via fq parameters.
 
 -Yonik

Query optimisation - multiple filter caches?

2007-08-15 Thread Jonathan Woods 
I'm trying to understand how best to integrate directly with Solr
(Java-to-Java in the same JVM) to make the most of its query optimisation -
chiefly, its caching of queries which merely filter rather than rank
results.
 
I notice that SolrIndexSearcher maintains a filter cache and so does
LuceneQueryOptimiser.  Shouldn't they be contributing to/using the same
cache, or are they used for different things?
 
Jon

Re: Query optimisation - multiple filter caches?

2007-08-15 Thread Yonik Seeley 
On 8/15/07, Jonathan Woods [EMAIL PROTECTED] wrote:
 I'm trying to understand how best to integrate directly with Solr
 (Java-to-Java in the same JVM) to make the most of its query optimisation -
 chiefly, its caching of queries which merely filter rather than rank
 results.

 I notice that SolrIndexSearcher maintains a filter cache and so does
 LuceneQueryOptimiser.  Shouldn't they be contributing to/using the same
 cache, or are they used for different things?

LuceneQueryOptimiser is no longer used since one can directly specify
filters via fq parameters.

-Yonik