ssd_cache
Similar tocache, but stores data on SSD and index in RAM. All cache dictionary settings related to update queue can also be applied to SSD cache dictionaries.
Cache contents are local to each server and are lost when a server restarts or is replaced. Do not use ssd_cache or complex_key_ssd_cache for reliable insert-time enrichment: an empty cache makes inserts depend on lookups to the dictionary source. In ClickHouse Cloud, autoscaling and managed node replacement make this condition more likely. Use a layout that loads the complete dictionary on each server instead; see Dictionary best practices.
Like cache, this layout keeps no record of which keys exist, so reading it as a table with SELECT ... FROM <dictionary> returns only the cells currently held that hold a value: it cannot discover keys absent from the cache, and it skips the default cells that record keys which were looked up but not found at the source. Resident cells that have expired are still re-requested from the source. See cache.
The dictionary key has the UInt64 type.
- DDL
- Configuration file
complex_key_ssd_cache
This type of storage is for use with composite keys. Similar tossd_cache.