Skip to content

dumpling: fix default column collation with upstream when dump table (#30531)#31776

Closed
ti-srebot wants to merge 1 commit into
pingcap:release-5.3from
ti-srebot:release-5.3-9f744cdf8266
Closed

dumpling: fix default column collation with upstream when dump table (#30531)#31776
ti-srebot wants to merge 1 commit into
pingcap:release-5.3from
ti-srebot:release-5.3-9f744cdf8266

Conversation

@ti-srebot
Copy link
Copy Markdown
Contributor

@ti-srebot ti-srebot commented Jan 18, 2022

cherry-pick #30531 to release-5.3
You can switch your code base to this Pull Request by using git-extras:

# In tidb repo:
git pr https://github.com/pingcap/tidb/pull/31776

After apply modifications, you can push your change to this PR via:

git push git@github.com:ti-srebot/tidb.git pr/31776:release-5.3-9f744cdf8266

What problem does this PR solve?

Issue Number: close #3420

Problem Summary: May miss default colum collation when dump create table.

What is changed and how it works?

Check List

Tests

  • Unit test

Release note

Dumpling add default column collation when dump create table.

Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
@ti-chi-bot
Copy link
Copy Markdown
Member

[REVIEW NOTIFICATION]

This pull request has not been approved.

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Details

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

@ti-chi-bot
Copy link
Copy Markdown
Member

@ti-srebot: This cherry pick PR is for a release branch and has not yet been approved by release team.
Adding the do-not-merge/cherry-pick-not-approved label.

To merge this cherry pick, it must first be approved by the collaborators.

AFTER it has been approved by collaborators, please ping the release team in a comment to request a cherry pick review.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@ti-srebot
Copy link
Copy Markdown
Contributor Author

/run-all-tests

@ti-chi-bot ti-chi-bot added do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. release-note Denotes a PR that will be considered when it comes time to generate release notes. and removed do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Jan 18, 2022
@ti-srebot ti-srebot added component/dumpling This is related to Dumpling of TiDB. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. type/5.3-cherry-pick labels Jan 18, 2022
@ti-chi-bot ti-chi-bot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Jan 18, 2022
@ti-srebot
Copy link
Copy Markdown
Contributor Author

@WizardXiao please accept the invitation then you can push to the cherry-pick pull requests. Comment with /cherry-pick-invite if the invitation is expired.
https://github.com/ti-srebot/tidb/invitations

@lance6716
Copy link
Copy Markdown
Contributor

wrong action

@lance6716 lance6716 closed this Jan 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

component/dumpling This is related to Dumpling of TiDB. do-not-merge/cherry-pick-not-approved release-note Denotes a PR that will be considered when it comes time to generate release notes. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. type/5.3-cherry-pick

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants