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: fix wrong index merge join plan for join key is not the prefix of index (#16894) #17365

Merged
merged 2 commits into from
May 25, 2020

Conversation

sre-bot
Copy link
Contributor

@sre-bot sre-bot commented May 22, 2020

cherry-pick #16894 to release-4.0


What problem does this PR solve?

Issue Number: close #16887

Problem Summary: consider the situations in issue.

The problem is caused by the planner, the join keys of index merge join must strictly meet the prefix of the inner index. In this case, the join key is:

admin_role_has_permissions.role_id

And index used:

(permission_id, role_id)

The data read from the inner to keep order is not actually ordered by the join key, which causes the index merge join to produce the wrong join result.

What is changed and how it works?

What's Changed: when the join keys do not strictly meet the prefix of the inner index. Don't generate the index merge join plan.

Related changes

  • Need to cherry-pick to the release branch

Check List

Tests

  • Unit test
  • Integration test

Side effects

  • Performance regression
    • Consumes more CPU

Release note

Fix planner incorrectly choose index merge join in some cases.

@sre-bot sre-bot requested review from a team as code owners May 22, 2020 10:09
@ghost ghost requested review from XuHuaiyu and a team and removed request for a team May 22, 2020 10:09
@sre-bot
Copy link
Contributor Author

sre-bot commented May 22, 2020

/run-all-tests

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

@lzmhhh123 lzmhhh123 added the priority/release-blocker This issue blocks a release. Please solve it ASAP. label May 22, 2020
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

@jebter
Copy link

jebter commented May 25, 2020

/merge

@sre-bot sre-bot added the status/can-merge Indicates a PR has been approved by a committer. label May 25, 2020
@sre-bot
Copy link
Contributor Author

sre-bot commented May 25, 2020

/run-all-tests

@sre-bot sre-bot merged commit 8ab4555 into pingcap:release-4.0 May 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/release-blocker This issue blocks a release. Please solve it ASAP. sig/execution SIG execution sig/planner SIG: Planner status/can-merge Indicates a PR has been approved by a committer. type/bugfix This PR fixes a bug. type/4.0-cherry-pick
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants