You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Kishen Das (Jira)" <ji...@apache.org> on 2021/01/11 23:28:00 UTC

[jira] [Updated] (HIVE-24618) Hive JDBC should use java.time.LocalDateTime

     [ https://issues.apache.org/jira/browse/HIVE-24618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kishen Das updated HIVE-24618:
------------------------------
    Summary: Hive JDBC should use java.time.LocalDateTime   (was: Hive JDBC should use timestamp in UTC)

> Hive JDBC should use java.time.LocalDateTime 
> ---------------------------------------------
>
>                 Key: HIVE-24618
>                 URL: https://issues.apache.org/jira/browse/HIVE-24618
>             Project: Hive
>          Issue Type: Bug
>          Components: JDBC
>            Reporter: Kishen Das
>            Assignee: Kishen Das
>            Priority: Major
>
> Hive moved away from java.sql.Timestamp to java.time.LocalDateTime ( https://issues.apache.org/jira/browse/HIVE-12192 ), in order to be consistent w.r.t timestamp field irrespective of the current time zone. For example: for time zones like America/Los_Angeles that alternate between PST and PDT, time can be shown based on effective current time zone, which is set in the current SQL session. Hive JDBC handler should follow suit and use LocalDateTime ( A date-time without a time-zone ), when doing the conversion.  
>  
> This issue is also more pronounced because of this bug in Java -> 
> [https://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8258586] . 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)