-
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
model: add schema name, table name to ddl job. #11561
Conversation
Codecov Report
@@ Coverage Diff @@
## master #11561 +/- ##
===========================================
Coverage 81.5429% 81.5429%
===========================================
Files 426 426
Lines 93368 93368
===========================================
Hits 76135 76135
Misses 11855 11855
Partials 5378 5378 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/Rest LGTM |
/LGTM |
/run-all-tests |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/run-all-tests |
/run-integration-common-test |
What problem does this PR solve?
Related parser PR: pingcap/parser#422
Before:
The schema name and table name maybe "" after the database or table droped.
This PR
(DDL 93 and 91 don't have name because it is the old version ddl job.)
TiDB used to only store the schema ID and table ID in DDL job info, When executing
admin show ddl jobs
, TiDB useinfoschema
to find schema/table name by the schema ID and table ID. But after we drop the database or table, this does not work any more.What is changed and how it works?
Check List
Tests
Unit test
Code changes
Has exported function/method change
Side effects
Related changes