Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Received-SPF: pass (athena.apache.org: domain of tim@elementspace.com
 designates 209.85.220.51 as permitted sender)
Message-ID: <52604AFD.1090000@elementspace.com>
Date: Thu, 17 Oct 2013 13:39:25 -0700
From: Tim Vaillancourt <tim@elementspace.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
 rv:1.9.2.24) Gecko/20111120 Icedove/3.1.16
MIME-Version: 1.0
To: solr-user@lucene.apache.org
Subject: Re: Skipping caches on a /select
References: 
 <CACtzgz29faZUmprizua0JsKbQ9Q8kVqq0EFC_YE=GnoTawWiNQ@mail.gmail.com>
 <CAB_8Yd8ybjeCEbwge5S8rT02ExQWjti1GPR_=CeGpT6OV4Dz1Q@mail.gmail.com>
In-Reply-To: 
 <CAB_8Yd8ybjeCEbwge5S8rT02ExQWjti1GPR_=CeGpT6OV4Dz1Q@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Thanks Yonik,

Does "cache=false" apply to all caches? The docs make it sound like it 
is for filterCache only, but I could be misunderstanding.

When I force a commit and perform a /select a query many times with 
"cache=false", I notice my query gets cached still, my guess is in the 
queryResultCache. At first the query takes 500ms+, then all subsequent 
requests take 0-1ms. I'll confirm this queryResultCache assumption today.

Cheers,

Tim

On 16/10/13 06:33 PM, Yonik Seeley wrote:
> On Wed, Oct 16, 2013 at 6:18 PM, Tim Vaillancourt<tim@elementspace.com>  wrote:
>> I am debugging some /select queries on my Solr tier and would like to see
>> if there is a way to tell Solr to skip the caches on a given /select query
>> if it happens to ALREADY be in the cache. Live queries are being inserted
>> and read from the caches, but I want my debug queries to bypass the cache
>> entirely.
>>
>> I do know about the "cache=false" param (that causes the results of a
>> select to not be INSERTED in to the cache), but what I am looking for
>> instead is a way to tell Solr to not read the cache at all, even if there
>> actually is a cached result for my query.
> Yeah, cache=false for "q" or "fq" should already not use the cache at
> all (read or write).
>
> -Yonik