Answering my own question: Looks like the default filterCache regenerator uses the old cache to re-executes queries in the context of the new searcher and does nothing with the old cache value.
So, the new searcher’s cache contents will be consistent with that searcher’s view, regardless of whether it was populated via autowarm. On 9/24/15, 11:28 AM, "Jeff Wartes" <jwar...@whitepages.com> wrote: > >If I configure my filterCache like this: ><filterCache class="solr.FastLRUCache" size="512" initialSize="512" >autowarmCount="10"/> > >and I have <= 10 distinct filter queries I ever use, does that mean I’ve >effectively disabled cache invalidation? So my cached filter query results >will never change? (short of JVM restart) > >I’m unclear on whether autowarm simply copies the value into the new >searcher’s cache or whether it tries to rebuild the results of the cached >filter query based on the new searcher’s view of the data. >
