Skip to content
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

failed to restore DDL when upstream has some different limit config from default value #45793

Closed
Leavrth opened this issue Aug 3, 2023 · 0 comments · Fixed by #45794
Closed
Assignees
Labels
affects-6.5 This bug affects the 6.5.x(LTS) versions. affects-7.1 This bug affects the 7.1.x(LTS) versions. affects-7.3 component/br This issue is related to BR of TiDB. severity/moderate type/bug The issue is confirmed as a bug.

Comments

@Leavrth
Copy link
Contributor

Leavrth commented Aug 3, 2023

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

  1. upstream, set some limit config, suche as table-column-count, to its max value.
  2. create a table with too many column or index.
  3. backup
  4. restore to downstream

2. What did you expect to see? (Required)

  1. success

3. What did you see instead (Required)

failed to restore for DDL check error.

4. What is your TiDB version? (Required)

master

@Leavrth Leavrth added the type/bug The issue is confirmed as a bug. label Aug 3, 2023
@Leavrth Leavrth self-assigned this Aug 3, 2023
@Leavrth Leavrth added severity/moderate affects-6.5 This bug affects the 6.5.x(LTS) versions. affects-7.1 This bug affects the 7.1.x(LTS) versions. affects-7.3 component/br This issue is related to BR of TiDB. labels Aug 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-6.5 This bug affects the 6.5.x(LTS) versions. affects-7.1 This bug affects the 7.1.x(LTS) versions. affects-7.3 component/br This issue is related to BR of TiDB. severity/moderate type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant