-
Notifications
You must be signed in to change notification settings - Fork 226
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
restore
command for ReplicatedMergeTree after DROP TABLE IF EXISTS ... should check replication path is exists in ZK and generate new path with predefined format, i.e. /clickhouse/tables/{cluster}/{shard}/{database}/{table}
#849
Comments
Hi @Slach, |
no this is a different issue, but could be related usign {uuid} in replication path always bad idea from my perspective do you mean restoring as a workaround you could change manually |
I will try the workaround tmr. Thanks |
you also could try to use
after that ReplicatedMergeTree will create on cluster with the same UUID
uuid is not related to backup |
if you will use restore_metadata_on_cluster and use restore --data only in first replica in each shard |
It worked ! Thank you. |
restore
command for ReplicatedMergeTree with --restore-database-mapping, should check replication path is exists in ZK and generate new path with predefined format, i.e. /clickhouse/tables/{cluster}/{shard}/{database}/{table}restore
command for ReplicatedMergeTree after DROP TABLE IF EXISTS ... should check replication path is exists in ZK and generate new path with predefined format, i.e. /clickhouse/tables/{cluster}/{shard}/{database}/{table}
No description provided.
The text was updated successfully, but these errors were encountered: