Dear Hive Developers, Following up on my previous mail, I have turned the timestamp proposal into a brief design doc <https://cwiki.apache.org/confluence/display/Hive/Different+TIMESTAMP+types> on the Hive wiki and created the HIVE-21348 <https://issues.apache.org/jira/browse/HIVE-21348> JIRA ("Execute the TIMESTAMP types roadmap") for tracking this effort with the following child tasks:
- HIVE-21002 <https://issues.apache.org/jira/browse/HIVE-21002> TIMESTAMP - Backwards incompatible change: Hive 3.1 reads back Avro and Parquet timestamps written by Hive 2.x incorrectly - HIVE-21290 <https://issues.apache.org/jira/browse/HIVE-21290>: Restore historical way of handling timestamps in Parquet while keeping the new semantics at the same time - HIVE-21291 <https://issues.apache.org/jira/browse/HIVE-21291>: Restore historical way of handling timestamps in Avro while keeping the new semantics at the same time - HIVE-21349 <https://issues.apache.org/jira/browse/HIVE-21349> TIMESTAMP WITHOUT TIME ZONE - HIVE-21359 <https://issues.apache.org/jira/browse/HIVE-21359> Parquet support for TIMESTAMP WITHOUT TIME ZONE - HIVE-21360 <https://issues.apache.org/jira/browse/HIVE-21360> Avro support for TIMESTAMP WITHOUT TIME ZONE - HIVE-21361 <https://issues.apache.org/jira/browse/HIVE-21361> ORC support for TIMESTAMP WITHOUT TIME ZONE - HIVE-21350 <https://issues.apache.org/jira/browse/HIVE-21350> TIMESTAMP WITH LOCAL TIME ZONE - HIVE-21353 <https://issues.apache.org/jira/browse/HIVE-21353> Use Instant instead of ZonedDateTime as the internal type for TIMESTAMP WITH LOCAL TIME ZONE - HIVE-21355 <https://issues.apache.org/jira/browse/HIVE-21355> Parquet support for TIMESTAMP WITH LOCAL TIME ZONE - HIVE-21357 <https://issues.apache.org/jira/browse/HIVE-21357> Avro support for TIMESTAMP WITH LOCAL TIME ZONE - HIVE-21358 <https://issues.apache.org/jira/browse/HIVE-21358> ORC support for TIMESTAMP WITH LOCAL TIME ZONE - HIVE-21351 <https://issues.apache.org/jira/browse/HIVE-21351> TIMESTAMP WITH TIME ZONE - No child JIRAs created yet. The most urgent tasks are probably the ones dealing with the backward incompatible change introduced in Hive 3.1. Please let me know if you have any questions or concerns. Thanks, Zoltan On Wed, Feb 20, 2019 at 3:56 PM Zoltan Ivanfi <z...@cloudera.com> wrote: > Hi, > > Last december we shared a timestamp harmonization proposal > <https://goo.gl/VV88c5> with the Hive, Spark and Impala communities. This > was followed by an extensive discussion in January that lead to various > updates and improvements to the proposal, as well as the creation of a new > document for file format components. February has been quiet regarding this > topic and the latest revision of the proposal has been steady in the recent > weeks. > > In short, the following is being proposed (please see the document for > details): > > - The TIMESTAMP WITHOUT TIME ZONE type should have LocalDateTime > semantics. > - The TIMESTAMP WITH LOCAL TIME ZONE type should have Instant > semantics. > - The TIMESTAMP WITH TIME ZONE type should have OffsetDateTime > semantics. > > This proposal is in accordance with the SQL standard and many major DB > engines. > > Based on the feedback we got I believe that the latest revision of the > proposal addresses the needs of all affected components, therefore I would > like to move forward and create JIRA-s and/or roadmap documentation pages > for the desired semantics of the different SQL types according to the > proposal. > > Please let me know if you have any remaning concerns about the proposal or > about the course of action outlined above. > > Thanks, > > Zoltan >
