database_replicated_allow_explicit_uuid
0 - Don’t allow to explicitly specify UUIDs for tables in Replicated databases. 1 - Allow. 2 - Allow, but ignore the specified UUID and generate a random one instead.database_replicated_allow_heavy_create
Allow long-running DDL queries (CREATE AS SELECT and POPULATE) in Replicated database engine. Note that it can block DDL queue for a long time.database_replicated_allow_only_replicated_engine
Allow creating a table in a database with theReplicated engine only if the table either replicates its own
data stored on disk or does not store its own data on disk.
This restriction applies only to table-owned on-disk data, including data on remote disks. It does not guarantee
the durability of in-memory data or data managed by external systems.
For example, ReplicatedMergeTree, in-memory engines such as Memory and Buffer, metadata-only engines
such as Merge and Alias, and external-storage or data lake engines such as S3 and AzureBlobStorage are
allowed. Non-replicated engines that store table data on disk, such as MergeTree, Log, File, and Set, are
rejected, including when their writable storage policy uses remote disks. Set and Join tables created with
SETTINGS persistent = 0 keep their data only in memory and are allowed.
Distributed, Remote, and RemoteSecure tables are allowed. Their optional local background INSERT queue
is a transient send buffer, not data of the table itself. It is not replicated, and setting
distributed_foreground_insert = 1 avoids the queue.
Cloud default value: 1.
database_replicated_allow_replicated_engine_arguments
0 - Don’t allow to explicitly specify ZooKeeper path and replica name for *MergeTree tables in Replicated databases. 1 - Allow. 2 - Allow, but ignore the specified path and use default one instead. 3 - Allow and don’t log a warning.database_replicated_always_detach_permanently
Execute DETACH TABLE as DETACH TABLE PERMANENTLY if database engine is Replicateddatabase_replicated_enforce_synchronous_settings
Enforces synchronous waiting for some queries (see also database_atomic_wait_for_drop_and_detach_synchronously, mutations_sync, alter_sync). Not recommended to enable these settings.database_replicated_initial_query_timeout_sec
Sets how long initial DDL query should wait for Replicated database to process previous DDL queue entries in seconds. Possible values:- Positive integer.
- 0 — Unlimited.