[
https://issues.apache.org/jira/browse/HIVE-10728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14568268#comment-14568268
]
Sergey Shelukhin commented on HIVE-10728:
-----------------------------------------
unix_timestamp/0 is non-deterministic, so different results are by design.
In existing code, results will be different depending on whether task fails or
not, for example (retrying will create different timestamp).
So it's not a backward incompatible change
> deprecate unix_timestamp(void) and make it deterministic
> --------------------------------------------------------
>
> Key: HIVE-10728
> URL: https://issues.apache.org/jira/browse/HIVE-10728
> Project: Hive
> Issue Type: Bug
> Reporter: Sergey Shelukhin
> Assignee: Sergey Shelukhin
> Attachments: HIVE-10728.01.patch, HIVE-10728.02.patch,
> HIVE-10728.03.patch, HIVE-10728.patch
>
>
> We have a proper current_timestamp function that is not evaluated at runtime.
> Behavior of unix_timestamp(void) is both surprising, and is preventing some
> optimizations on the other overload since the function becomes
> non-deterministic.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
