You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
clickhouse-operator already generate some macros values during runtime, like {cluster} {shard} {replica}
why do you need to define other macros? which is your use case?
I want to transfer the ck cluster on Independent deployment server to k8s ck cluster,this cluster have different macros , and different database table have different macros , i do not want change the sql
Is your indepentent deployment server just single instance of clickhouse-server?
Is this kubernetes cluster or single docker container or standalone systemd service?
Hi @zouwenjie00 , have you checked system.macros table? By default, operator already generates macros similarly to what you want, populating it with proper values for every node.
HI:
I want to create custom macros ,like this:
and want get shardname 、replicaname、podname to set its,but it is not effect
The text was updated successfully, but these errors were encountered: