executor: skip inner rows when the join keys contains NULL #7255
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
zz-jason
added
type/bugfix
|
/run-all-tests |
winoros
reviewed
Aug 2, 2018
winoros
approved these changes
Aug 3, 2018
|
/run-unit-test |
birdstorm
added
status/LGT2
birdstorm
approved these changes
Aug 5, 2018
zz-jason
added a commit
to zz-jason/tidb
that referenced
this pull request
Aug 7, 2018
zz-jason
added a commit
that referenced
this pull request
Aug 8, 2018
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.
What have you changed? (mandatory)
This PR skips the inner rows which contains
NULLvalue in the join key for "Merge Join" and "Index Join", thus they behaves the same as "Hash Join".What is the type of the changes? (mandatory)
How has this PR been tested? (mandatory)
existing tests.
Does this PR affect documentation (docs/docs-cn) update? (mandatory)
Does this PR affect tidb-ansible update? (mandatory)
Does this PR need to be added to the release notes? (mandatory)
Yes
Refer to a related PR or issue link (optional)
to #7226
Benchmark result if necessary (optional)
Add a few positive/negative examples (optional)