You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@druid.apache.org by cw...@apache.org on 2019/12/15 03:56:18 UTC
[incubator-druid] branch 0.17.0-incubating updated: docs - clarify
cache parameters (#9020) (#9039)
This is an automated email from the ASF dual-hosted git repository.
cwylie pushed a commit to branch 0.17.0-incubating
in repository https://gitbox.apache.org/repos/asf/incubator-druid.git
The following commit(s) were added to refs/heads/0.17.0-incubating by this push:
new c7aa375 docs - clarify cache parameters (#9020) (#9039)
c7aa375 is described below
commit c7aa37590d5204eaa0427b637e0984774d8cdeea
Author: Clint Wylie <cw...@apache.org>
AuthorDate: Sat Dec 14 19:56:08 2019 -0800
docs - clarify cache parameters (#9020) (#9039)
---
docs/querying/caching.md | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/docs/querying/caching.md b/docs/querying/caching.md
index 20482da..6b6811a 100644
--- a/docs/querying/caching.md
+++ b/docs/querying/caching.md
@@ -38,12 +38,17 @@ Segment-level caching does require Druid to merge the per-segment results on eac
from the cache. For this reason, whole-query result level caching can be more efficient if invalidation due to real-time
ingestion is not an issue.
+
+## Using and populating cache
+
+All caches have a pair of parameters that control the behavior of how individual queries interact with the cache, a 'use' cache parameter, and a 'populate' cache parameter. These settings must be enabled at the service level via [runtime properties](../configuration/index.md) to utilize cache, but can be controlled on a per query basis by setting them on the [query context](../querying/query-context.md). The 'use' parameter obviously controls if a query will utilize cached results. The ' [...]
+
## Query caching on Brokers
Brokers support both segment-level and whole-query result level caching. Segment-level caching is controlled by the
parameters `useCache` and `populateCache`. Whole-query result level caching is controlled by the parameters
`useResultLevelCache` and `populateResultLevelCache` and [runtime properties](../configuration/index.md)
-`druid.broker.cache.*`..
+`druid.broker.cache.*`.
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 (< 5 servers). Populating segment-level caches on
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org