-
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
ddl: do not reference owner_id for specific system DDL (#53332) #53334
ddl: do not reference owner_id for specific system DDL (#53332) #53334
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: D3Hunter, tangenta, wjhuang2016 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## release-8.1 #53334 +/- ##
================================================
Coverage ? 71.1938%
================================================
Files ? 1465
Lines ? 421420
Branches ? 0
================================================
Hits ? 300025
Misses ? 100941
Partials ? 20454
Flags with carried forward coverage won't be shown. Click here to find out more.
|
This is an automated cherry-pick of #53332
What problem does this PR solve?
Issue Number: close #53327
Problem Summary:
In #53234, TiDB fails to execute below upgrade DDL, because it needs to access
owner_id
fromtidb_mdl_info
.What changed and how does it work?
For the DDLs related to system tables, we skip using
owner_id
field to prevent above DDL failed.Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.