-
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
planner: fix wrong schema when to solve the schema name in CTE (#57253) #57333
planner: fix wrong schema when to solve the schema name in CTE (#57253) #57333
Conversation
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
/retest |
/retest |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hawkingrei, qw4990 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 |
[LGTM Timeline notifier]Timeline:
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## release-7.1 #57333 +/- ##
================================================
Coverage ? 73.4515%
================================================
Files ? 1213
Lines ? 382045
Branches ? 0
================================================
Hits ? 280618
Misses ? 83494
Partials ? 17933 |
This is an automated cherry-pick of #57253
What problem does this PR solve?
Issue Number: close #54582
Problem Summary:
What changed and how does it work?
when to
adjustCTEPlanOutputName
, we will force the current db name as the query schema. but it is the root cause. sometime query will set specific schema name. we must follow this name to get meta.Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.