[
https://issues.apache.org/jira/browse/HIVE-9917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14394938#comment-14394938
]
Jason Dere commented on HIVE-9917:
----------------------------------
Hmm, that's surprising - I think there are a lot of places where Hive
implicitly converts timestamp to a numeric type. Stuff like
comparison/sum()/avg() (all of which I wish had simply been disallowed -
semantics would have been more clear if those had been disallowed and user had
been forced to use UDF). I think the example you used was not a good one since
it may correspond to 0 in unix epoch time. I tried this:
{noformat}
hive> select cast(current_timestamp as bigint);
OK
1428087647
{noformat}
> After HIVE-3454 is done, make int to timestamp conversion configurable
> ----------------------------------------------------------------------
>
> Key: HIVE-9917
> URL: https://issues.apache.org/jira/browse/HIVE-9917
> Project: Hive
> Issue Type: Improvement
> Reporter: Aihua Xu
> Assignee: Aihua Xu
> Attachments: HIVE-9917.patch
>
>
> After HIVE-3454 is fixed, we will have correct behavior of converting int to
> timestamp. While the customers are using such incorrect behavior for so long,
> better to make it configurable so that in one release, it will default to
> old/inconsistent way and the next release will default to new/consistent way.
> And then we will deprecate it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
