[
https://issues.apache.org/jira/browse/HIVE-21353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16780744#comment-16780744
]
Jesus Camacho Rodriguez commented on HIVE-21353:
------------------------------------------------
+1
> 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
> Priority: Major
>
> 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)
