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

Restore still check the empty cluster even when filter is specified #51009

Closed
3pointer opened this issue Feb 6, 2024 · 1 comment · Fixed by #51010
Closed

Restore still check the empty cluster even when filter is specified #51009

3pointer opened this issue Feb 6, 2024 · 1 comment · Fixed by #51010
Labels
affects-7.3 affects-7.4 affects-7.5 This bug affects the 7.5.x(LTS) versions. affects-7.6 component/br This issue is related to BR of TiDB. severity/major type/bug The issue is confirmed as a bug.

Comments

@3pointer
Copy link
Contributor

3pointer commented Feb 6, 2024

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

  1. restore full with --filter arguments to a non-empty cluster.

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

restore start

3. What did you see instead (Required)

restore not pass requirements-check.

4. What is your TiDB version? (Required)

since v7.3

@3pointer 3pointer added the type/bug The issue is confirmed as a bug. label Feb 6, 2024
@benmaoer
Copy link

benmaoer commented Feb 6, 2024

Lost affect version tag

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-7.3 affects-7.4 affects-7.5 This bug affects the 7.5.x(LTS) versions. affects-7.6 component/br This issue is related to BR of TiDB. severity/major type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants