Hi, On Mon, Nov 24, 2014 at 11:51 AM, Lasse Schou <[email protected]> wrote: > > The way I understand the Shard Query Cache > <http://www.elasticsearch.org/guide/en/elasticsearch/reference/1.4/index-modules-shard-query-cache.html>, > it invalidates *ALL *cached results in a shard when the shard refreshes, > given that *ANY *data in the shard has changed. >
This is correct. > My data changes all the time, but I'd like to keep some of my query > results cached for a while - say 1 minute. > > My refresh interval (5 sec) cannot be changed because I need near-realtime > searches for other query types. > > I can read that there is a "indices.cache.query.expire" config setting > where the general TTL of all Shard Query Caches can be set, but the docs > specify that this shouldn't really be used because all cached results are > invalidated anyway upon refresh. > The thing is that we wanted this cache to give accurate results: no matter if it is enabled or not you are going to get the same results. (just like the filter caches and fielddata caches). In your case, I think the best option would be to put a cache in front of elasticsearch? -- Adrien Grand -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAL6Z4j4u3LMmm3EcLiPH3aacx4QJM70Vfbn2kzKWhVZOxDY52Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
