[
https://issues.apache.org/jira/browse/HIVE-14412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rui Li updated HIVE-14412:
--------------------------
Resolution: Fixed
Hadoop Flags: Incompatible change,Reviewed
Fix Version/s: 3.0.0
Release Note:
HIVE-14412 adds 'timestamp with time zone' data type to Hive. The full
qualified input format of this type is 'yyyy-MM-dd HH:mm:ss[.SSS...]
ZoneId/ZoneOffset', where the time and zone parts are optional. If time part is
absent, a default '00:00:00.0' will be used. If zone part is absent, the system
time zone will be used. Examples of valid ZoneId and ZoneOffset are:
America/Los_Angeles and GMT+08:00. All timestamp with time zone will be
converted and stored as UTC retaining the instant. E.g. '2017-04-14 18:00:00
Asia/Shanghai' will be converted and stored as '2017-04-14 10:00:00.0 Z'.
'timestamptz' is accepted as a type alias for 'timestamp with time zone'.
Conversion between date/timestamp and timestamp with time zone is done using
the system time zone.
'time' becomes a reserved key word after HIVE-14412, thus can break user
queries where 'time' is used as identifiers. If users want to continue use
'time' as identifiers, they have to escape it with '`' (backtick).
Status: Resolved (was: Patch Available)
Pushed to master. Thanks guys for the review!
> Add timestamp with time zone
> ----------------------------
>
> 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
> Fix For: 3.0.0
>
> Attachments: HIVE-14412.10.patch, HIVE-14412.11.patch,
> HIVE-14412.12.patch, HIVE-14412.13.patch, HIVE-14412.1.patch,
> HIVE-14412.2.patch, HIVE-14412.3.patch, HIVE-14412.4.patch,
> HIVE-14412.5.patch, HIVE-14412.6.patch, HIVE-14412.7.patch,
> HIVE-14412.8.patch, HIVE-14412.9.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.15#6346)
