{{ message }}
Add the setting to ignore ON CLUSTER clause for replicated databases#92872
Merged
evillique merged 3 commits intoDec 24, 2025
Merged
Conversation
evillique
reviewed
Dec 23, 2025
evillique
reviewed
Dec 23, 2025
evillique
left a comment
Member
There was a problem hiding this comment.
The new setting should be added in src/Core/SettingsChangesHistory.cpp
Contributor
Co-authored-by: Nikolay Degterinsky <43110995+evillique@users.noreply.github.com>
evillique
approved these changes
Dec 24, 2025
Merged
via the queue into
ClickHouse:master
with commit Dec 24, 2025
3561526
127 of 131 checks passed
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Changelog category (leave one):
Changelog entry (a [user-readable short description]
It is possible to execute DDL queries with
ON CLUSTERclause for a Replicated database if theignore_on_cluster_for_replicated_databasesetting is enabled. In this case, the cluster name will be ignored.Documentation entry for user-facing changes
Basically reopening #84176. Main use case is for a seamless migration of a database to replicated engine, so users can still use their old ON CLUSTER ddl queries without change.
In some cases ignoring cluster name can be unexpected behaviour, so using a setting for this feature can fix that.