Repository navigation
Need to Make ClickHouse Cloud-Mode an Option #5785
Description
With the release of the official ClickHouse Kubernetes operator, the new standard for production self-hosted ClickHouse clusters is to make use of the replicated database engine. This produces similar functionality to ClickHouse Cloud, in that it does not work with CREATE TABLE ... AS SELECT. SQLMesh already has a workaround for this with cloud mode. This mode can only be enabled by having "clickhouse.cloud" in the host name. I have added a CNAME to my dns to have my clickhouse host be resolved by clickhouse.cloud.my.domain.net to get around this. In the long run it would be good to have this property be a setting in ClickHouse connection config. Read more on the new paradigm here: https://clickhouse.com/docs/clickhouse-operator/overview
Activity
cookieark7 commentedon Sep 3, 2026
I'd like to pick this one up.
Plan: add
cloud_modetoClickhouseConnectionConfigas an optional bool. DefaultNonekeeps the current"clickhouse.cloud" in hostdetection so existing configs are untouched;trueforces it on for self-hosted replicated clusters;falseforces it off, including on a real*.clickhouse.cloudhost, on the basis that an explicit setting should win.Keeping the name
cloud_modeto match the existing property andEngineRunMode.CLOUD— happy to rename if you'd prefer something that reads less like "the managed product" now that replicated self-hosted is a case.cloud_modealso isn't documented today, so I'd add it to the connection options table inclickhouse.mdand cover the replicated-database case in the modes-of-operation section.@cams-data if you're still running the CNAME workaround, it'd be useful to have this verified against a real replicated cluster once it's up — I can only test the generated SQL locally.