Problem Summary
There is currently significant friction when migrating schemas from ClickHouse Cloud to Self-Hosted environments (OSS).
DDL exported from ClickHouse Cloud frequently uses the SharedMergeTree engine. When executing these scripts on standard clickhouse-server images (tested on v25.12), the engine is unrecognized, resulting in:
Code: 56. DB::Exception: Unknown table engine SharedMergeTree. (UNKNOWN_STORAGE)
Impact on Migration
For users operating in hybrid environments or migrating workloads to EKS/Kubernetes, this requires manual refactoring of every CREATE TABLE statement to replace SharedMergeTree with ReplicatedMergeTree or MergeTree. This break in syntax compatibility makes CI/CD and schema synchronization between Cloud and OSS unnecessarily difficult.
Additional Information
ClickHouse Version: 25.12
Environment: AWS EKS
Operator: Altinity ClickHouse Operator
Problem Summary
There is currently significant friction when migrating schemas from ClickHouse Cloud to Self-Hosted environments (OSS).
DDL exported from ClickHouse Cloud frequently uses the SharedMergeTree engine. When executing these scripts on standard clickhouse-server images (tested on v25.12), the engine is unrecognized, resulting in:
Code: 56. DB::Exception: Unknown table engine SharedMergeTree. (UNKNOWN_STORAGE)
Impact on Migration
For users operating in hybrid environments or migrating workloads to EKS/Kubernetes, this requires manual refactoring of every CREATE TABLE statement to replace SharedMergeTree with ReplicatedMergeTree or MergeTree. This break in syntax compatibility makes CI/CD and schema synchronization between Cloud and OSS unnecessarily difficult.
Additional Information
ClickHouse Version: 25.12
Environment: AWS EKS
Operator: Altinity ClickHouse Operator