[HIVE-21353] Use Instant instead of ZonedDateTime as the internal type for TIMESTAMP WITH LOCAL TIME ZONE

• Type: Task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Assignee: Unassigned
• Reporter: Zoltan Ivanfi
• Created: 28/Feb/19 16:17
• Updated: 27/Feb/24 22:23

Description

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

Issue Links

• blocks: HIVE-21355 Parquet support for TIMESTAMP WITH LOCAL TIME ZONE
• blocks: HIVE-21357 Avro support for TIMESTAMP WITH LOCAL TIME ZONE
• blocks: HIVE-21358 ORC support for TIMESTAMP WITH LOCAL TIME ZONE
• is a child of: HIVE-21350 TIMESTAMP WITH LOCAL TIME ZONE
• supercedes: HIVE-21094 Store TIMESTAMP WITH LOCAL TIME ZONE in UTC instead of writer's time zone