You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Zoltan Ivanfi (JIRA)" <ji...@apache.org> on 2019/02/28 16:18:00 UTC
[jira] [Created] (HIVE-21353) Use Instant instead of ZonedDateTime
as the internal type for TIMESTAMP WITH LOCAL TIME ZONE
Zoltan Ivanfi created HIVE-21353:
------------------------------------
Summary: Use Instant instead of ZonedDateTime as the internal type for TIMESTAMP WITH LOCAL TIME ZONE
Key: HIVE-21353
URL: https://issues.apache.org/jira/browse/HIVE-21353
Project: Hive
Issue Type: Task
Reporter: Zoltan Ivanfi
Currently Hive uses the ZonedDateTime class to represent TIMESTAMP WITH LOCAL TIME ZONE values although that type shall behave like an Instant.
In fact, the behaviour of TIMESTAMP WITH LOCAL TIME ZONE has already been updated to match the desired Instant semantics, but it still uses the ZonedDateTime class in the background, which is counter-intuitive and results in overly complex logic. Additionally, it leads to the strange side-effect that in textfiles the values are stored in the writer's local time, and the writer's zone is stored with each individual value.
Using Instant instead of ZonedDateTime will:
* simplify the internal logic
* allow saving UTC-normalized values into textfile tables
* allow adding support for tables of file formats other than textfile
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)