fix(sharding): Distributed migrations table #8
Conversation
This file contains 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
This will work with clickhouse-operator
macobo
force-pushed
the
distributed-migrations-table
branch
from
3dc13a0 to
5c3c2d8
Compare
|
Verified this works - merging to make integrating with main repo easier. |
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.
Part of PostHog/posthog#8652
clickhouse-operator only creates tables backed by
Distributedengine onto new shards, see Altinity/clickhouse-operator#903 for more details. We automatically create PostHog tables manually (see PostHog/posthog#8912) but clickhouse migrations also need to be runnable no matter what clickhouse node we hit.