Invalidating query cache

This impairs the ability of the Druid cluster to scale well. Segment-level caching is controlled by the query context parameters .

For this reason, whole-query result level caching can be more efficient if invalidation due to real-time ingestion is not an issue.The following are considerations that should determine whether or not caching the results of a Named Query is helpful.Each time the Named Query is called, if the arguments passed differ from those used to create the current cache, a new cache is created.Enabling segment-level caching on the Broker can yield faster results than if query caches were enabled on Historicals for small clusters.This is the recommended setup for smaller production clusters (), results from Historicals are returned on a per segment basis, and Historicals will not be able to do any local result merging.

Search for invalidating query cache:

invalidating query cache-74invalidating query cache-86invalidating query cache-44

Leave a Reply

Your email address will not be published. Required fields are marked *

One thought on “invalidating query cache”