[
https://issues.apache.org/jira/browse/HIVE-10728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14563391#comment-14563391
]
Sergey Shelukhin commented on HIVE-10728:
-----------------------------------------
[~alangates] can you comment?
The other way would be to rewrite the (void) overload to act like
current_timestamp, that way both would be deterministic.
Given that it wasn't deterministic in the first place, returning same value is
a compatible behavior :)
> 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.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)
