[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 ] Pengcheng Xiong updated HIVE-15863: --- Target Version/s: 3.0.0 (was: 2.2.0) > 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 > > 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)
[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: (was: 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 > > 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)
[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: --- Status: Open (was: Patch Available) > 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 > > 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)
[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: (was: 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)
[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)
[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)
[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: (was: 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)
[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)
[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: (was: 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)
[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)
[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: --- Status: Patch Available (was: In Progress) > 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)
