mirror of
https://github.com/ClickHouse/ClickHouse.git
synced 2024-11-26 17:41:59 +00:00
Update storing-data.md
This commit is contained in:
parent
133446a404
commit
a6b1586b17
@ -155,7 +155,7 @@ Example of configuration for versions earlier than 22.8:
|
|||||||
<endpoint>...</endpoint>
|
<endpoint>...</endpoint>
|
||||||
... s3 configuration ...
|
... s3 configuration ...
|
||||||
<data_cache_enabled>1</data_cache_enabled>
|
<data_cache_enabled>1</data_cache_enabled>
|
||||||
<data_cache_max_size>10Gi</data_cache_max_size>
|
<data_cache_max_size>2147483648</data_cache_max_size>
|
||||||
</s3>
|
</s3>
|
||||||
</disks>
|
</disks>
|
||||||
<policies>
|
<policies>
|
||||||
@ -172,7 +172,7 @@ Cache **configuration settings**:
|
|||||||
|
|
||||||
- `path` - path to the directory with cache. Default: None, this setting is obligatory.
|
- `path` - path to the directory with cache. Default: None, this setting is obligatory.
|
||||||
|
|
||||||
- `max_size` - maximum size of the cache in bytes or in readable format (`ki, Mi, Gi, etc`, example `10Gi`). When the limit is reached, cache files are evicted according to the cache eviction policy. Default: None, this setting is obligatory.
|
- `max_size` - maximum size of the cache in bytes or in readable format, e.g. `ki, Mi, Gi, etc`, example `10Gi` (such format works starting from `22.9` version). When the limit is reached, cache files are evicted according to the cache eviction policy. Default: None, this setting is obligatory.
|
||||||
|
|
||||||
- `cache_on_write_operations` - allow to turn on `write-through` cache (caching data on any write operations: `INSERT` queries, background merges). Default: `false`. The `write-through` cache can be disabled per query using setting `enable_filesystem_cache_on_write_operations` (data is cached only if both cache config settings and corresponding query setting are enabled).
|
- `cache_on_write_operations` - allow to turn on `write-through` cache (caching data on any write operations: `INSERT` queries, background merges). Default: `false`. The `write-through` cache can be disabled per query using setting `enable_filesystem_cache_on_write_operations` (data is cached only if both cache config settings and corresponding query setting are enabled).
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user