You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Jesus Camacho Rodriguez (JIRA)" <ji...@apache.org> on 2017/02/09 14:28:41 UTC

[jira] [Updated] (HIVE-15863) Calendar inside DATE, TIME and TIMESTAMP literals for Calcite should have UTC timezone

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

Jesus Camacho Rodriguez updated HIVE-15863:
-------------------------------------------
    Attachment: HIVE-15863.patch

> Calendar inside DATE, TIME and TIMESTAMP literals for Calcite should have UTC timezone
> --------------------------------------------------------------------------------------
>
>                 Key: HIVE-15863
>                 URL: https://issues.apache.org/jira/browse/HIVE-15863
>             Project: Hive
>          Issue Type: Bug
>          Components: CBO
>    Affects Versions: 2.2.0
>            Reporter: Jesus Camacho Rodriguez
>            Assignee: Jesus Camacho Rodriguez
>         Attachments: HIVE-15863.patch
>
>
> Related to CALCITE-1623.
> At query preparation time, Calcite uses a Calendar to hold the value of DATE, TIME, TIMESTAMP literals. It assumes that Calendar has a UTC (GMT) time zone, and bad things might happen if it does not. Currently, we pass the Calendar object with user timezone from Hive. We need to pass it with UTC timezone and make the inverse conversion when we go back from Calcite to Hive.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)