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

tidb-lightning import wrong data if user doesn't has right permission #31088

Closed
glorv opened this issue Dec 28, 2021 · 1 comment · Fixed by #31089
Closed

tidb-lightning import wrong data if user doesn't has right permission #31088

glorv opened this issue Dec 28, 2021 · 1 comment · Fixed by #31089
Assignees
Labels
affects-5.2 This bug affects 5.2.x versions. affects-5.3 This bug affects 5.3.x versions. component/lightning This issue is related to Lightning of TiDB. severity/major type/bug The issue is confirmed as a bug.

Comments

@glorv
Copy link
Contributor

glorv commented Dec 28, 2021

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

Use tidb-lightning to import data into a v5.3.0 cluster with (new_collations_enabled_on_first_bootstrap=true). The user in tidb-lightning's config doesn't has permission to access to table mysql.tidb

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

The import should either return an error or import success.

3. What did you see instead (Required)

TiDB-Lightning return success but data in target db is not consistent.

4. What is your TiDB version? (Required)

@github-actions
Copy link

Please check whether the issue should be labeled with 'affects-x.y' or 'fixes-x.y.z', and then remove 'needs-more-info' label.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-5.2 This bug affects 5.2.x versions. affects-5.3 This bug affects 5.3.x versions. component/lightning This issue is related to Lightning 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