> ## Documentation Index
> Fetch the complete documentation index at: https://clickhouse.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# use_* session settings
> ClickHouse session settings in the use_* generated group.
export const SettingsInfoBlock = ({type, default_value, changeable_without_restart}) => {
return
;
};
These settings are available in [system.settings](/docs/reference/system-tables/settings) and are autogenerated from [source](https://github.com/ClickHouse/ClickHouse/blob/master/src/Core/Settings.cpp).
use\_async\_executor\_for\_materialized\_views
Use async and potentially multithreaded execution of materialized view query, can speedup views processing during INSERT, but also consume more memory.
use\_cache\_for\_count\_from\_files
Enables caching of rows number during count from files in table functions `file`/`s3`/`url`/`hdfs`/`azureBlobStorage`.
Enabled by default.
use\_client\_time\_zone
Use client timezone for interpreting DateTime string values, instead of adopting server timezone.
Uses compact format for storing blocks for background (`distributed_foreground_insert`) INSERT into tables with `Distributed` engine.
Possible values:
* 0 — Uses `user[:password]@host:port#default_database` directory format.
* 1 — Uses `[shard{shard_index}[_replica{replica_index}]]` directory format.
- with `use_compact_format_in_distributed_parts_names=0` changes from cluster definition will not be applied for background INSERT.
- with `use_compact_format_in_distributed_parts_names=1` changing the order of the nodes in the cluster definition, will change the `shard_index`/`replica_index` so be aware.
use\_concurrency\_control
Respect the server's concurrency control (see the `concurrent_threads_soft_limit_num` and `concurrent_threads_soft_limit_ratio_to_cores` global server settings). If disabled, it allows using a larger number of threads even if the server is overloaded (not recommended for normal usage, and needed mostly for tests).
use\_constant\_folding\_in\_index\_analysis
Substitute partition-level constants into the filter predicate when analyzing per-part primary key and skip indexes.
When the partition key appears in the filter together with primary-key or skip-index columns, this lets index analysis fold the partition value separately within each part. It is most useful for disjunctive filters whose branches target different partitions. For example, with `PARTITION BY a` and `ORDER BY b`:
```sql theme={null}
SELECT * FROM t WHERE (a = 1 AND b >= 1) OR (a = 2 AND b > 10) OR (a = 3 AND b > 10)
```
For the part in partition `a = 1` the condition folds to `b >= 1`, while for partitions `a = 2` and `a = 3` it folds to `b > 10`, so each part is analyzed with the predicate that actually applies to it.
Possible values:
* 0 — Disabled.
* 1 — Enabled.
use\_hash\_table\_stats\_for\_join\_reordering
Enable using collected hash table statistics for cardinality estimation during join reordering
use\_hedged\_requests
Enables hedged requests logic for remote queries. It allows to establish many connections with different replicas for query.
New connection is enabled in case existent connection(s) with replica(s) were not established within `hedged_connection_timeout`
or no data was received within `receive_data_timeout`. Query uses the first connection which send non empty progress packet (or data packet, if `allow_changing_replica_until_first_data_packet`);
other connections are cancelled. Queries with `max_parallel_replicas > 1` are supported.
Enabled by default.
Cloud default value: `0`.
use\_hive\_partitioning
When enabled, ClickHouse will detect Hive-style partitioning in path (`/name=value/`) in file-like table engines [File](/docs/reference/functions/table-functions/file#hive-style-partitioning)/[S3](/docs/reference/functions/table-functions/s3#hive-style-partitioning)/[URL](/docs/reference/functions/table-functions/url#hive-style-partitioning)/[HDFS](/docs/reference/functions/table-functions/hdfs#hive-style-partitioning)/[AzureBlobStorage](/docs/reference/functions/table-functions/azureBlobStorage#hive-style-partitioning) and will allow to use partition columns as virtual columns in the query. These virtual columns will have the same names as in the partitioned path, but starting with `_`.
use\_join\_disjunctions\_push\_down
Enable pushing OR-connected parts of JOIN conditions down to the corresponding input sides ("partial pushdown").
This allows storage engines to filter earlier, which can reduce data read.
The optimization is semantics-preserving and is applied only when each top-level OR branch contributes at least one deterministic
predicate for the target side.
use\_legacy\_to\_time
When enabled, allows to use legacy toTime function, which converts a date with time to a certain fixed date, while preserving the time.
Otherwise, uses a new toTime function, that converts different type of data into the Time type.
The old legacy function is also unconditionally accessible as toTimeWithFixedDate.
use\_lightweight\_primary\_key\_index\_analysis
Optimize primary key index analysis for `MergeTree` tables with long primary keys.
When enabled, the run time of index analysis mainly depends on the complexity of the query's filter (the key columns it actually uses), not on the length of the primary key — so extending the sorting key has negligible extra overhead on index analysis for queries that filter on only a few of its columns.
Possible values:
* 0 — Disabled. All primary key columns are processed during index analysis.
* 1 — Enabled.
use\_parquet\_metadata\_cache
If turned on, parquet format may utilize the parquet metadata cache.
Possible values:
* 0 - Disabled
* 1 - Enabled
use\_primary\_key
Use the primary key to prune granules during query execution for MergeTree tables.
Possible values:
* 0 — Disabled.
* 1 — Enabled.
use\_reader\_executor
Experimental. Route reads through the new pipeline `ReaderExecutor` instead of the legacy matryoshka of read buffers. Falls back to the legacy path for configurations the executor does not yet support.
Use roaring bitmap for iceberg positional deletes.
use\_streaming\_marks\_compression
When loading marks for MergeTree parts, compress them into the in-memory representation one block at a time (streaming) instead of materializing the full plain marks array first. This significantly reduces peak memory usage during marks loading for compact parts with many substreams (e.g. tables with JSON columns and write\_marks\_for\_substreams\_in\_compact\_parts enabled).
use\_strict\_insert\_block\_limits
When enabled, strictly enforces both minimum and maximum insert block size limits.
A block is emitted when:
* Min thresholds (AND): Both min\_insert\_block\_size\_rows AND min\_insert\_block\_size\_bytes are reached.
* Max thresholds (OR): Either max\_insert\_block\_size\_rows OR max\_insert\_block\_size\_bytes is reached.
When disabled, a block is emitted when:
* Min thresholds (OR): min\_insert\_block\_size\_rows OR min\_insert\_block\_size\_bytes is reached.
**Note**: If max settings are smaller than min settings, the max limits take precedence and blocks will be emitted before min thresholds are reached.
**Note**: This setting is automatically disabled for async inserts, because async inserts attach per-entry deduplication tokens that are incompatible with block splitting that is needed for enforcement of strict limits.
Disabled by default.
Use structure from insertion table instead of schema inference from data. Possible values: 0 - disabled, 1 - enabled, 2 - auto
use\_uncompressed\_cache
Whether to use a cache of uncompressed blocks. Accepts 0 or 1. By default, 0 (disabled).
Using the uncompressed cache (only for tables in the MergeTree family) can significantly reduce latency and increase throughput when working with a large number of short queries. Enable this setting for users who send frequent short requests. Also pay attention to the [uncompressed\_cache\_size](/docs/reference/settings/server-settings/settings#uncompressed_cache_size) configuration parameter (only set in the config file) – the size of uncompressed cache blocks. By default, it is 8 GiB. The uncompressed cache is filled in as needed and the least-used data is automatically deleted.
For queries that read at least a somewhat large volume of data (one million rows or more), the uncompressed cache is disabled automatically to save space for truly small queries. This means that you can keep the 'use\_uncompressed\_cache' setting always set to 1.
use\_with\_fill\_by\_sorting\_prefix
Columns preceding WITH FILL columns in ORDER BY clause form sorting prefix. Rows with different values in sorting prefix are filled independently