planner: reorder inner joins simplified from outer joins (#22392) #22402
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
/run-all-tests |
ti-srebot
added
sig/planner
|
@eurekaka you're already a collaborator in bot's repo. |
eurekaka
force-pushed
the
release-4.0-dd5bfc39490e
branch
from
2a07683 to
6d17216
Compare
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
eurekaka
force-pushed
the
release-4.0-dd5bfc39490e
branch
from
6d17216 to
69bd8f0
Compare
|
/run-all-tests |
ti-srebot
added
status/LGT2
qw4990
approved these changes
Jan 18, 2021
ti-srebot
added
status/LGT3
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
cherry-pick #22392 to release-4.0
You can switch your code base to this Pull Request by using git-extras:
# In tidb repo: git pr https://github.com/pingcap/tidb/pull/22402After apply modifications, you can push your change to this PR via:
What problem does this PR solve?
Issue Number: close #22384
Problem Summary:
Plan for query containing outer join is not optimal.
What is changed and how it works?
What's Changed:
Add
flagJoinReOrderwhen buildingLogicalJoinregardless of the join types.joinReorderSolveritself can check if the reorder is applicable.How it Works:
Related changes
Check List
Tests
Side effects
N/A
Release note