Shard query cache and filters with _cache:false

Is the shard query cache disabled if a filter is specified in
query.filter.filtered.bool.must clause has _cache: false? It makes some
intuitive sense if it's the case, but looking over the source code
https://github.com/elastic/elasticsearch/blob/1.4/src/main/java/org/elasticsearch/indices/cache/query/IndicesQueryCache.java#L169-L200
(we're
using 1.4.3), I can't see any reason why this would happen yet it seems to
on most of our queries (confirmed it's enabled in our settings at 2% of
heap).

--
Mike Sukmanowsky
Aspiring Digital Carpenter

p: +1 (416) 953-4248
e: mike.sukmanowsky@gmail.com

facebook http://facebook.com/mike.sukmanowsky | twitter
http://twitter.com/msukmanowsky | LinkedIn
http://www.linkedin.com/profile/view?id=10897143 | github
https://github.com/msukmanowsky

--
Please update your bookmarks! We have moved to https://discuss.elastic.co/

You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAOH6cu5CdGB0HS%2BraR_4JZ%2BQwSZ--JVxcD6FQSYvewmwvH4q3A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

The query cache is completely independent from the filter cache, so
disabling caching on a filter won't disable the query cache.

On Mon, May 25, 2015 at 11:04 PM, Mike Sukmanowsky <
mike.sukmanowsky@gmail.com> wrote:

Is the shard query cache disabled if a filter is specified in
query.filter.filtered.bool.must clause has _cache: false? It makes some
intuitive sense if it's the case, but looking over the source code
https://github.com/elastic/elasticsearch/blob/1.4/src/main/java/org/elasticsearch/indices/cache/query/IndicesQueryCache.java#L169-L200 (we're
using 1.4.3), I can't see any reason why this would happen yet it seems to
on most of our queries (confirmed it's enabled in our settings at 2% of
heap).

--
Mike Sukmanowsky
Aspiring Digital Carpenter

p: +1 (416) 953-4248
e: mike.sukmanowsky@gmail.com

facebook http://facebook.com/mike.sukmanowsky | twitter
http://twitter.com/msukmanowsky | LinkedIn
http://www.linkedin.com/profile/view?id=10897143 | github
https://github.com/msukmanowsky

--
Please update your bookmarks! We have moved to https://discuss.elastic.co/

You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAOH6cu5CdGB0HS%2BraR_4JZ%2BQwSZ--JVxcD6FQSYvewmwvH4q3A%40mail.gmail.com
https://groups.google.com/d/msgid/elasticsearch/CAOH6cu5CdGB0HS%2BraR_4JZ%2BQwSZ--JVxcD6FQSYvewmwvH4q3A%40mail.gmail.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
Adrien

--
Please update your bookmarks! We have moved to https://discuss.elastic.co/

You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAO5%3DkAhsMtdu2ptvpfctcoz59pvVfnqsnrdJ2FhmksgHWyS6gQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.