You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Aihua Xu (JIRA)" <ji...@apache.org> on 2015/04/02 17:37:53 UTC

[jira] [Updated] (HIVE-9917) After HIVE-3454 is done, make int to timestamp conversion configurable

     [ https://issues.apache.org/jira/browse/HIVE-9917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aihua Xu updated HIVE-9917:
---------------------------
    Attachment: HIVE-9917.patch

Add the new configuration hive.int.timestamp.conversion.in.seconds. If the value is true, then boolean/tinyint/smallint/int/bigint will be interpreted as seconds, otherwise, in milliseconds. The default value is false to be backward-compatible. 

Such flag is handled during query compilation time for both regular query and vectorized query. 

> 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)