-
Notifications
You must be signed in to change notification settings - Fork 4.7k
HIVE-28917: NPE in merge statement when checking nullability of joini… #5781
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
Conversation
iceberg/iceberg-handler/src/test/queries/negative/merge_with_null_check_on_joining_col.q
Outdated
Show resolved
Hide resolved
5efdfe4
to
ef385f5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not very familiar with this part of the code but given that the test pass and there are no new failures I am leaning towards accepting the PR. Left some small comments/questions but we should be close to merge this unless someone else has thoughts on the proposal.
iceberg/iceberg-handler/src/test/queries/positive/merge_with_null_check_on_joining_col.q
Show resolved
Hide resolved
iceberg/iceberg-handler/src/test/queries/positive/merge_with_null_check_on_joining_col.q
Show resolved
Hide resolved
iceberg/iceberg-handler/src/test/queries/positive/merge_with_null_check_on_joining_col.q
Outdated
Show resolved
Hide resolved
ef385f5
to
b4427fa
Compare
|
@zabetak @kasakrisz |
@soumyakanti3578, @kasakrisz , @zabetak : seems like the precommit of this patch was green, but when the commit was merged, something else was already committed that altered the expected q.out, hence this failure now: can someone revert or update the q.out as soon as possible? thanks in advance |
…ng column in matched clause
What changes were proposed in this pull request?
When TOK_FROM is not present in the AST for MERGE statements, return
DestClausePrefix.MERGE
.Why are the changes needed?
Without this we could get an NPE as explained in HIVE-28917
Does this PR introduce any user-facing change?
No
How was this patch tested?