allow_coalescing_columns_in_partition_or_order_key
When enabled, allows coalescing columns in a CoalescingMergeTree table to be used in the partition or sorting key.allow_commit_order_projection
Enables commit-order projections that store_block_number and _block_offset virtual columns, preserving original insertion order through merges.
Requires enable_block_number_column and enable_block_offset_column to be enabled.
allow_dimensions_outside_sorting_key
InAggregatingMergeTree, background merges collapse rows that share the same value of the sorting
key, combining their aggregate states. A column that is neither part of the sorting key nor an
aggregate-state measure (AggregateFunction or SimpleAggregateFunction) is a dimension: after
a merge it keeps an arbitrary value of one of the collapsed rows, which silently produces wrong
results for queries that GROUP BY or filter on it (see
https://github.com/ClickHouse/ClickHouse/issues/751).
By default, such a schema is rejected when the table is created. Enable this setting if the column is
functionally dependent on the sorting key (so all collapsed rows share the same value) and the
behavior is intentional.
The check applies only to tables that actually aggregate (those with at least one aggregate-state
column) and is skipped when allow_tuple_element_aggregation is enabled.
allow_floating_point_partition_key
Enables to allow floating-point number as a partition key. Possible values:0— Floating-point partition key not allowed.1— Floating-point partition key allowed.