-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
global index: drop global index or drop table but not delete global index range #40953
Comments
/label severity/minor |
@L-maple: The label(s) In response to this:
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 ti-community-infra/tichi repository. |
/assign @L-maple |
@Defined2014 Yes, the issue can be closed~ /close |
/close |
@L-maple: Closing this issue. In response to this:
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. |
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
I find the bug by debugging. I haven't find a way to show deleted regions correctly, because delete index is async.
when ddl is in onDropIndex reorg state, delete global index means partitionIDs should be nil, like the following. Otherwise, the logic would try to delete partitions'
2. What did you expect to see? (Required)
dropping global index / drop table, but not delete global index range.
3. What did you see instead (Required)
dropping global index delete table partitions' index.
4. What is your TiDB version? (Required)
master
| Release Version: v6.6.0-alpha-290-g6676ca816-dirty
Edition: Community
Git Commit Hash: 6676ca8
Git Branch: local/fix_drop_global_index_master
UTC Build Time: 2023-02-01 09:01:32
GoVersion: go1.19.4
Race Enabled: false
TiKV Min Version: 6.2.0-alpha
Check Table Before Drop: false
Store: unistore |
The text was updated successfully, but these errors were encountered: