OK, so cache=false and cost=100 should do it, see:
http://searchhub.org/2012/02/22/custom-security-filtering-in-solr/
Best,
Erick
On Wed, Dec 4, 2013 at 5:56 AM, Dmitry Kan <solrexp...@gmail.com> wrote:
> Thanks Yonik.
>
> For our use case, we would like to skip caching only one particular filter
> cache, yet apply a high cost for it to make sure it executes last of all
> filter queries.
>
> So this means, the rest of the fqs will execute and cache as usual.
>
>
>
>
> On Tue, Dec 3, 2013 at 9:58 PM, Yonik Seeley <yo...@heliosearch.com>
> wrote:
>
> > On Tue, Dec 3, 2013 at 4:45 AM, Dmitry Kan <solrexp...@gmail.com> wrote:
> > > ok, we were able to confirm the behavior regarding not caching the
> filter
> > > query. It works as expected. It does not cache with {!cache=false}.
> > >
> > > We are still looking into clarifying the cost assignment: i.e. whether
> it
> > > works as expected for long boolean filter queries.
> >
> > Yes, filters should be ordered by cost (cheapest first) whenever you
> > use {!cache=false}
> >
> > -Yonik
> > http://heliosearch.com -- making solr shine
> >
>
>
>
> --
> Dmitry
> Blog: http://dmitrykan.blogspot.com
> Twitter: twitter.com/dmitrykan
>
