hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Dere (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-9917) After HIVE-3454 is done, make int to timestamp conversion configurable
Date Sat, 18 Apr 2015 00:39:59 GMT

    [ https://issues.apache.org/jira/browse/HIVE-9917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14500959#comment-14500959
] 

Jason Dere commented on HIVE-9917:
----------------------------------

I'm looking at the qfile output changes, to make sure that the files look the same as they
did before HIVE-3454. Most of the files look as they did before, except for vectorization_decimal_date.q.out.
One example of this is that there is a count(*) query with a filter, and the result changes
from 5996 to 6058 after HIVE-3454, to 6026 with this patch.

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

Mime
View raw message