[
https://issues.apache.org/jira/browse/HIVE-14412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15489157#comment-15489157
]
Rui Li commented on HIVE-14412:
-------------------------------
Thank you guys for your inputs. Like Xuefu said, the standard name is TIMESTAMP
WITH TIME ZONE. Most popular DBs support this data type, e.g. Oracle, DB2,
PostgreSQL. I'll try if we can handle spaces in type name.
I haven't looked at ORC/vectorization support. But I think it's easy to
implement because the new type is basically just timestamp plus an extra
integer. We can do it in follow up tasks.
> 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
>
>
> 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
(v6.3.4#6332)
