[
https://issues.apache.org/jira/browse/HIVE-9917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14487917#comment-14487917
]
Jason Dere commented on HIVE-9917:
----------------------------------
Ah ok. Actually, I would prefer to have the output back to the way it was
pre-HIVE-3454, to confirm that between HIVE-3454 and this Jira, we haven't
broken anything in the existing tests. And then have the new tests toggle
hive.int.timestamp.conversion.in.second to true/false so we can see the
timestamp conversion behavior change.
> 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)
