Test the migration with TiDB Serverless branching - #1
Open
shiyuhang0 wants to merge 2 commits into
Open
shiyuhang0 wants to merge 2 commits into
shiyuhang0 wants to merge 2 commits into
Conversation
|
The latest updates on TiDB Serverless Branch. Learn more about branching GitHub integration↗︎
|
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
1 participant
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.
In order to test the migration, we added a GitHub action to run the migration in the created branch. The branch copies the data from TiDB serverless, ensuring we find any potential errors in the migration.
In this example, we want to add a unique index in the title field for the articles table. (The seed already loads the same title in TiDB Serverless)
branching helps us to test the migration and then we can merge this PR and apply the migration to the production cluster.