[
https://issues.apache.org/jira/browse/HIVE-14412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15488638#comment-15488638
]
Jason Dere commented on HIVE-14412:
-----------------------------------
Check if there are any issues with
TypeInfoParser/PrimitiveObjectInspectorUtils. When i did interval I wasn't sure
about if the spaces would be problematic internally within Hive and used
underscores. In the Hive SQL parser you should be able to have "TIMESTAMP WITH
TIME ZONE" be recognized as a synonym for TIMESTAMPTZ when parsing type names,
but internally (serde params, describe table) the type name will currently show
up using the type name that was registered in PrimitiveObjectInspectorUtils.
> 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)
