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

planner: resolveFromPlan when tblName.colName exists in having clause #18349

Merged
merged 4 commits into from
Jul 8, 2020

Conversation

XuHuaiyu
Copy link
Contributor

@XuHuaiyu XuHuaiyu commented Jul 3, 2020

What problem does this PR solve?

Issue Number: close #18384

Problem Summary:

What is changed and how it works?

What's Changed:
For SQL like select a+1 from t having t.a, we need to resolve it from the plan and select fields both.

How it Works:

Related changes

  • Need to cherry-pick to the release branch

Check List

Tests

  • Integration test

Side effects

N/A

Release note

  • Fix unknown column error for sql like select a from t having t.a

@XuHuaiyu XuHuaiyu changed the title [TEST] Issue17852 [TEST] Issue18384 Jul 6, 2020
@XuHuaiyu XuHuaiyu changed the title [TEST] Issue18384 planner: resolveFromPlan when tblName.colName exists in having clause Jul 6, 2020
@XuHuaiyu XuHuaiyu marked this pull request as ready for review July 6, 2020 13:44
@XuHuaiyu XuHuaiyu requested a review from a team as a code owner July 6, 2020 13:44
@XuHuaiyu XuHuaiyu requested review from hanfei1991 and removed request for a team July 6, 2020 13:44
@XuHuaiyu XuHuaiyu requested review from winoros, qw4990 and eurekaka and removed request for hanfei1991 July 6, 2020 13:48
@XuHuaiyu
Copy link
Contributor Author

XuHuaiyu commented Jul 6, 2020

/run-all-tests

@XuHuaiyu XuHuaiyu added the type/bugfix This PR fixes a bug. label Jul 6, 2020
Copy link
Contributor

@qw4990 qw4990 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ti-srebot
Copy link
Contributor

@qw4990, Thanks for your review, however we are sorry that your vote won't be count. You are not a reviewer or committer or co-leader or leader for the related sigs:planner(slack).

@XuHuaiyu XuHuaiyu added the status/LGT1 Indicates that a PR has LGTM 1. label Jul 7, 2020
Copy link
Contributor

@eurekaka eurekaka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ti-srebot
Copy link
Contributor

@eurekaka,Thanks for your review.

@codecov
Copy link

codecov bot commented Jul 7, 2020

Codecov Report

Merging #18349 into master will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             master     #18349   +/-   ##
===========================================
  Coverage   79.3923%   79.3923%           
===========================================
  Files           540        540           
  Lines        144665     144665           
===========================================
  Hits         114853     114853           
  Misses        20524      20524           
  Partials       9288       9288           

@XuHuaiyu
Copy link
Contributor Author

XuHuaiyu commented Jul 8, 2020

/merge

@ti-srebot
Copy link
Contributor

Sorry @XuHuaiyu, you don't have permission to trigger auto merge event on this branch. You are not a committer or co-leader or leader for the related sigs:planner(slack).

@eurekaka
Copy link
Contributor

eurekaka commented Jul 8, 2020

/merge

@ti-srebot
Copy link
Contributor

Sorry @eurekaka, you don't have permission to trigger auto merge event on this branch. The number of LGTM for this PR is 1 while it needs 2 at least

Copy link
Contributor

@lzmhhh123 lzmhhh123 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ti-srebot ti-srebot removed the status/LGT1 Indicates that a PR has LGTM 1. label Jul 8, 2020
@ti-srebot ti-srebot added the status/LGT2 Indicates that a PR has LGTM 2. label Jul 8, 2020
@ti-srebot
Copy link
Contributor

@lzmhhh123,Thanks for your review.

@lzmhhh123
Copy link
Contributor

/merge

@ti-srebot ti-srebot added the status/can-merge Indicates a PR has been approved by a committer. label Jul 8, 2020
@ti-srebot
Copy link
Contributor

/run-all-tests

@ti-srebot ti-srebot merged commit 62979f6 into pingcap:master Jul 8, 2020
ti-srebot pushed a commit to ti-srebot/tidb that referenced this pull request Jul 8, 2020
@ti-srebot
Copy link
Contributor

cherry pick to release-3.0 in PR #18432

ti-srebot pushed a commit to ti-srebot/tidb that referenced this pull request Jul 8, 2020
@ti-srebot
Copy link
Contributor

cherry pick to release-3.1 in PR #18433

ti-srebot pushed a commit to ti-srebot/tidb that referenced this pull request Jul 8, 2020
@ti-srebot
Copy link
Contributor

cherry pick to release-4.0 in PR #18434

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sig/planner SIG: Planner status/can-merge Indicates a PR has been approved by a committer. status/LGT2 Indicates that a PR has LGTM 2. type/bugfix This PR fixes a bug.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

unexpected unknown column error
5 participants