HIVE-26653: Wrong results when (map) joining multiple tables on parti… #6165
+175
−28
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.



…tion column
What changes were proposed in this pull request?
In INNER joins, when we only project the small table's joining key, we can run into a situation when the hashmap's value is empty. Then, if we serialize the empty value, we will get
NULLs. Instead we should just copy thekeyinto the vectorized batch.Why are the changes needed?
Explained in detail: https://issues.apache.org/jira/browse/HIVE-26653
Does this PR introduce any user-facing change?
No
How was this patch tested?
Added unit tests in
TestMapJoinOperator.java. The original issue is not reproducible anymore because of an unrelated patch, as explained in the Jira.