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.

Sign up for GitHub

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

Jump to bottom

br: clp restore db/tbl behavior is different from br sql #58168

Closed
BornChanger opened this issue Dec 11, 2024 · 0 comments · Fixed by #58211
Closed

br: clp restore db/tbl behavior is different from br sql #58168

BornChanger opened this issue Dec 11, 2024 · 0 comments · Fixed by #58211
Labels
affects-6.1 This bug affects the 6.1.x(LTS) versions. 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.5 This bug affects the 7.5.x(LTS) versions. affects-8.1 This bug affects the 8.1.x(LTS) versions. affects-8.5 This bug affects the 8.5.x(LTS) versions. component/br This issue is related to BR of TiDB. severity/major type/bug The issue is confirmed as a bug.

Comments

@BornChanger
Copy link
Contributor

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

  1. create table db1.t1 on the cluster
  2. insert some data into db1.t1
  3. run restore tiup br restore table db1.t1 to restore to the table

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

ERROR 8125 (HY000): Restore failed: table already exists

3. What did you see instead (Required)

Error: failed to validate checksum: [BR:Restore:ErrRestoreChecksumMismatch]restore checksum mismatch

4. What is your TiDB version? (Required)

master
@BornChanger BornChanger added component/br This issue is related to BR of TiDB. severity/major type/bug The issue is confirmed as a bug. labels Dec 11, 2024
@BornChanger BornChanger added affects-6.1 This bug affects the 6.1.x(LTS) versions. 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.5 This bug affects the 7.5.x(LTS) versions. affects-8.1 This bug affects the 8.1.x(LTS) versions. affects-8.5 This bug affects the 8.5.x(LTS) versions. and removed may-affects-5.4 This bug maybe affects 5.4.x versions. may-affects-6.1 may-affects-6.5 may-affects-7.1 may-affects-7.5 may-affects-8.1 may-affects-8.5 labels Dec 11, 2024
@RidRisR RidRisR mentioned this issue Dec 12, 2024
Merged
13 tasks
@ti-chi-bot ti-chi-bot bot closed this as completed in c1083de Dec 13, 2024
This was referenced Dec 13, 2024
Merged
Merged
ti-chi-bot bot pushed a commit that referenced this issue Dec 13, 2024
@ti-chi-bot
br: make table existence check unified on different br client (#58211) (
85c160d 
#58245)

close #58168
ti-chi-bot bot pushed a commit that referenced this issue Dec 13, 2024
@ti-chi-bot
br: make table existence check unified on different br client (#58211) (
c44264f 
#58244)

close #58168
This was referenced Dec 14, 2024
Merged
Open
Open
ti-chi-bot bot pushed a commit that referenced this issue Dec 15, 2024
@ti-chi-bot
br: make table existence check unified on different br client (#58211) (
a4f58fe 
#58262)

close #58168
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
affects-6.1 This bug affects the 6.1.x(LTS) versions. 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.5 This bug affects the 7.5.x(LTS) versions. affects-8.1 This bug affects the 8.1.x(LTS) versions. affects-8.5 This bug affects the 8.5.x(LTS) versions. component/br This issue is related to BR of TiDB. severity/major type/bug The issue is confirmed as a bug.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

br: make table existence check unified on different br client RidRisR/tidb
1 participant
@BornChanger