Return-Path: Delivered-To: apmail-lucene-java-user-archive@www.apache.org Received: (qmail 48540 invoked from network); 23 Aug 2006 08:22:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 23 Aug 2006 08:22:25 -0000 Received: (qmail 11676 invoked by uid 500); 23 Aug 2006 08:22:18 -0000 Delivered-To: apmail-lucene-java-user-archive@lucene.apache.org Received: (qmail 11655 invoked by uid 500); 23 Aug 2006 08:22:18 -0000 Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-user@lucene.apache.org Delivered-To: mailing list java-user@lucene.apache.org Received: (qmail 11642 invoked by uid 99); 23 Aug 2006 08:22:18 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Aug 2006 01:22:18 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [169.229.70.167] (HELO rescomp.berkeley.edu) (169.229.70.167) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Aug 2006 01:22:17 -0700 Received: by rescomp.berkeley.edu (Postfix, from userid 1007) id 43E905B77A; Wed, 23 Aug 2006 01:21:50 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by rescomp.berkeley.edu (Postfix) with ESMTP id 3DF927F403 for ; Wed, 23 Aug 2006 01:21:50 -0700 (PDT) Date: Wed, 23 Aug 2006 01:21:50 -0700 (PDT) From: Chris Hostetter To: Lucene Users Subject: Re: Solr Cache In-Reply-To: <44EBAAF6.10106@gmail.com> Message-ID: References: <44EBAAF6.10106@gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N : It looks like Solr does not use a simple cached queryfilter as a query : cache. Why is this? Is a cache queryfilter not efficient enough? Is this : alternate method just so you can easily load the cache from an old : Searcher to a new Searcher? Any info appreciated. This would probably be better addressed on the solr-user mailing list -- please post any followup question there. I'll through out some high level answers though in case any one else is interested... * there's nothign to stop a solr request handler from using QueryFilter's if they want (i have and do) * Solr has several types of caches for different things * the "filterCache" has the most direct conceptual mapping to how a QueryFilter and CachedWrapperFilter work. The big benefits it has are: - the DocSet API allows for more memory efficient representations of small sets of documents then just a BitSet - it can be configured with a size and replacement strategy (CachedWrapperFilter is more for things that can live "forever" relative the IndexReader) -Hoss --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org For additional commands, e-mail: java-user-help@lucene.apache.org