> ## 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.

# cluster_table_* session settings

> ClickHouse session settings in the cluster_table_* generated group.

These settings are available in [system.settings](https://clickhouse.com/docs/reference/system-tables/settings.md) and are autogenerated from [source](https://github.com/ClickHouse/ClickHouse/blob/master/src/Core/Settings.cpp).

## cluster\_table\_function\_buckets\_batch\_size

Type

UInt64

Default

0

Defines the approximate size of a batch (in bytes) used in distributed processing of tasks in cluster table functions with `bucket` split granularity. The system accumulates data until at least this amount is reached. The actual size may be slightly larger to align with data boundaries.

## cluster\_table\_function\_pushed\_down\_filter

This is an internal setting that should not be used directly. The initiator of a query with a cluster table function sets it for the replicas to the serialized filter on the table, so that the replicas drop the rows that do not pass it before sending them.

## cluster\_table\_function\_split\_by\_split\_offsets

Type

Bool

Default

0

With `bucket` split granularity, when the table metadata records the file size and the row group offsets (`split_offsets` in Iceberg), cut files into byte ranges on these offsets without reading them; each task reads the row groups that start in its range. Otherwise, and on a hit in the query condition cache, the initiator reads the footer of every file.

Requires all servers of the cluster to support it: a task with a byte range cannot be sent to a server of an older version.

## cluster\_table\_function\_split\_granularity

Type

ObjectStorageGranularityLevel

Default

file

Controls how data is split into tasks when executing a CLUSTER TABLE FUNCTION.

This setting defines the granularity of work distribution across the cluster:

* `file` — each task processes an entire file.
* `bucket` — tasks are created per internal data block within a file (for example, Parquet row groups).

Choosing finer granularity (like `bucket`) can improve parallelism when working with a small number of large files.
For instance, if a Parquet file contains multiple row groups, enabling `bucket` granularity allows each group to be processed independently by different workers.
