This is an automated email from the ASF dual-hosted git repository.
gian pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-druid.git
The following commit(s) were added to refs/heads/master by this push:
new 0c3bb47 Change hybrid cache default types in docs to caffeine (#6182)
0c3bb47 is described below
commit 0c3bb4755805822e535e9a7bd3504b9edce949ff
Author: Jonathan Wei <[email protected]>
AuthorDate: Fri Aug 17 09:17:43 2018 -0700
Change hybrid cache default types in docs to caffeine (#6182)
---
docs/content/configuration/index.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/docs/content/configuration/index.md
b/docs/content/configuration/index.md
index 992d1df..5eb03a6 100644
--- a/docs/content/configuration/index.md
+++ b/docs/content/configuration/index.md
@@ -1453,9 +1453,9 @@ If there is an L1 miss and L2 hit, it will also populate
L1.
|Property|Description|Default|
|--------|-----------|-------|
-|`druid.cache.l1.type`|type of cache to use for L1 cache. See
`druid.cache.type` configuration for valid types.|`local`|
-|`druid.cache.l2.type`|type of cache to use for L2 cache. See
`druid.cache.type` configuration for valid types.|`local`|
-|`druid.cache.l1.*`|Any property valid for the given type of L1 cache can be
set using this prefix. For instance, if you are using a `local` L1 cache,
specify `druid.cache.l1.sizeInBytes` to set its size.|defaults are the same as
for the given cache type.|
+|`druid.cache.l1.type`|type of cache to use for L1 cache. See
`druid.cache.type` configuration for valid types.|`caffeine`|
+|`druid.cache.l2.type`|type of cache to use for L2 cache. See
`druid.cache.type` configuration for valid types.|`caffeine`|
+|`druid.cache.l1.*`|Any property valid for the given type of L1 cache can be
set using this prefix. For instance, if you are using a `caffeine` L1 cache,
specify `druid.cache.l1.sizeInBytes` to set its size.|defaults are the same as
for the given cache type.|
|`druid.cache.l2.*`|Prefix for L2 cache settings, see description for
L1.|defaults are the same as for the given cache type.|
|`druid.cache.useL2`|A boolean indicating whether to query L2 cache, if it's a
miss in L1. It makes sense to configure this to `false` on historical nodes, if
L2 is a remote cache like `memcached`, and this cache also used on brokers,
because in this case if a query reached historical it means that a broker
didn't find corresponding results in the same remote cache, so a query to the
remote cache from historical is guaranteed to be a miss.|`true`|
|`druid.cache.populateL2`|A boolean indicating whether to put results into L2
cache.|`true`|
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
