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 point-get db privilege check #12268

Merged
merged 5 commits into from
Sep 23, 2019
Merged

planner/core: fix point-get db privilege check #12268

merged 5 commits into from
Sep 23, 2019

Conversation

lysu
Copy link
Contributor

@lysu lysu commented Sep 18, 2019

What problem does this PR solve?

current point-get code path checks db privilege by current db and miss check db1 privilege for query using db.tbl1.

and see more detail in test case.

What is changed and how it works?

check privilege using db in ast tree if it exists.

Check List

Tests

  • Unit test
  • Integration test

Code changes

  • impl

Side effects

  • n/a

Related changes

  • Need to cherry-pick to the release branch

Release note

  • planner/core: fix point-get db privilege check

This change is Reviewable

@lysu lysu added type/bugfix This PR fixes a bug. component/privilege labels Sep 18, 2019
@lysu
Copy link
Contributor Author

lysu commented Sep 18, 2019

/run-all-tests

@codecov
Copy link

codecov bot commented Sep 18, 2019

Codecov Report

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

@@             Coverage Diff             @@
##             master     #12268   +/-   ##
===========================================
  Coverage   81.1786%   81.1786%           
===========================================
  Files           454        454           
  Lines         99079      99079           
===========================================
  Hits          80431      80431           
  Misses        12880      12880           
  Partials       5768       5768

Copy link
Member

@zz-jason zz-jason left a comment

Choose a reason for hiding this comment

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

LGTM

@zz-jason zz-jason added the status/LGT1 Indicates that a PR has LGTM 1. label Sep 18, 2019
@lysu lysu requested a review from jackysp September 23, 2019 03:08
Copy link
Member

@jackysp jackysp left a comment

Choose a reason for hiding this comment

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

LGTM

@jackysp jackysp added status/can-merge Indicates a PR has been approved by a committer. status/LGT2 Indicates that a PR has LGTM 2. and removed status/LGT1 Indicates that a PR has LGTM 1. labels Sep 23, 2019
@sre-bot
Copy link
Contributor

sre-bot commented Sep 23, 2019

/run-all-tests

@sre-bot sre-bot merged commit 0cb06e6 into pingcap:master Sep 23, 2019
@sre-bot
Copy link
Contributor

sre-bot commented Sep 23, 2019

cherry pick to release-3.0 failed

@sre-bot
Copy link
Contributor

sre-bot commented Sep 23, 2019

cherry pick to release-2.1 failed

@sre-bot
Copy link
Contributor

sre-bot commented Sep 23, 2019

cherry pick to release-3.1 failed

@cyliu0
Copy link
Contributor

cyliu0 commented Nov 6, 2019

@lysu This PR has been labeled with needs-cherry-pick-3.1. Plz cherry pick this one to release-3.1

@lysu
Copy link
Contributor Author

lysu commented Nov 6, 2019

@cyliu0 done #13220

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/privilege 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.

5 participants