Repository navigation
HIVE-27741 handle Invalid timezone value in to_utc_timestamp() UDF - #5014
Conversation
aturoczy
left a comment
There was a problem hiding this comment.
The change is fine. Need a test re-run and green output.
zratkai
left a comment
There was a problem hiding this comment.
Please check the comments and fixes.
zratkai
left a comment
There was a problem hiding this comment.
Please check my comments, changes.
|
@okumin @simhadri-g could you please review? |
|
@okumin @simhadri-g could you please review? Refactored to use ZoneId instead of TimeZone. |
okumin
left a comment
There was a problem hiding this comment.
+1 with some minor cosmetic comments.
This could be an incompatible change. But I understand the current behavior is surprising and it sounds better to throw an error(or put NULL at least). The final judgment will be done by a committer.
|
|
@okumin @simhadri-g could you please review this? |
|
Looks good to me. Note that you finally need approval from a committer |
deniskuzZ
left a comment
There was a problem hiding this comment.
LGTM, minor code-style comments
…row exception instead a default value Change-Id: I68ee1783614b4b74093df0dddb613fa860ed202a
|




Change-Id: I68ee1783614b4b74093df0dddb613fa860ed202a
What changes were proposed in this pull request?
The to_utc_timestamp() UDF used UTC when the given timezone was invalid. It throws exception in this case to avoid data inconsistency.
Why are the changes needed?
To avoid data inconsistency in case of invalid timezone.
Does this PR introduce any user-facing change?
Yes. The to_utc_timestamp() UDF will throw exception in case of invalid timezone.
Is the change a dependency upgrade?
No.
How was this patch tested?
Unit test.