[
https://issues.apache.org/jira/browse/HIVE-9917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14395132#comment-14395132
]
Aihua Xu commented on HIVE-9917:
--------------------------------
There are some UDFs such as UDFToBoolean, UDFToLong and vectorized ones
requiring to take hive.int.timestamp.conversion.in.seconds parameters. I will
try to do that in HIVE-10202 to handle timestamp to int conversion and let this
jira focus on int to timestamp conversion.
Regarding comparison/sum()/avg(), I checked the comparison, internally it
always use milliseconds conversion, but since it's comparison, it works fine,
not sure if we want to handle the parameter in here. For sum()/avg(), we are
converting to double (so no int conversion issue).
> 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)
