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/core: fix not null flag for using and natural join #13735

Merged
merged 2 commits into from
Nov 26, 2019

Conversation

alivxxx
Copy link
Contributor

@alivxxx alivxxx commented Nov 26, 2019

What problem does this PR solve?

When there is using clause or natural in outer join, the not null flag for inner plan is not properly reset.

What is changed and how it works?

Reset the not null flag for the inner child of using and natural join when build the schema.

Check List

Tests

  • Unit test

Code changes

  • Has exported function/method change

Side effects

  • None

Related changes

  • Need to cherry-pick to the release branch

Release note

  • Reset the not null flag properly for natural outer join and outer join with using clause.

@alivxxx alivxxx added type/bugfix This PR fixes a bug. sig/planner SIG: Planner labels Nov 26, 2019
@codecov
Copy link

codecov bot commented Nov 26, 2019

Codecov Report

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

@@             Coverage Diff             @@
##             master     #13735   +/-   ##
===========================================
  Coverage   80.2607%   80.2607%           
===========================================
  Files           473        473           
  Lines        117127     117127           
===========================================
  Hits          94007      94007           
  Misses        15801      15801           
  Partials       7319       7319

Copy link
Member

@winoros winoros left a comment

Choose a reason for hiding this comment

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

lgtm

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

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

@eurekaka eurekaka added the status/can-merge Indicates a PR has been approved by a committer. label Nov 26, 2019
@eurekaka
Copy link
Contributor

Does this PR need to be cherry-picked?

@alivxxx
Copy link
Contributor Author

alivxxx commented Nov 26, 2019

Yes, updated the label.

@sre-bot
Copy link
Contributor

sre-bot commented Nov 26, 2019

/run-all-tests

@sre-bot sre-bot merged commit 3a7d2a1 into pingcap:master Nov 26, 2019
@alivxxx alivxxx deleted the not-null branch November 26, 2019 06:30
@sre-bot
Copy link
Contributor

sre-bot commented Nov 26, 2019

cherry pick to release-3.0 failed

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. type/bugfix This PR fixes a bug.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants