Rui Li commented on HIVE-14412:

Most of the recent failures are because "TIME" is added as a new key word so it 
can't be used as column name. So I have to rename the columns in the qtests. 
This can also require users to update their current queries. Do you guys think 
this is acceptable?

> Add a timezone-aware timestamp
> ------------------------------
>                 Key: HIVE-14412
>                 URL: https://issues.apache.org/jira/browse/HIVE-14412
>             Project: Hive
>          Issue Type: Sub-task
>          Components: Hive
>            Reporter: Rui Li
>            Assignee: Rui Li
>         Attachments: HIVE-14412.1.patch, HIVE-14412.2.patch, 
> HIVE-14412.3.patch, HIVE-14412.4.patch, HIVE-14412.5.patch, HIVE-14412.5.patch
> Java's Timestamp stores the time elapsed since the epoch. While it's by 
> itself unambiguous, ambiguity comes when we parse a string into timestamp, or 
> convert a timestamp to string, causing problems like HIVE-14305.
> To solve the issue, I think we should make timestamp aware of timezone.

This message was sent by Atlassian JIRA

Reply via email to