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

Posted to issues@hive.apache.org by "Sergio Peña (JIRA)" <ji...@apache.org> on 2017/06/28 22:10:00 UTC

[jira] [Reopened] (HIVE-16231) Parquet timestamp may be stored differently since HIVE-12767

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

Sergio Peña reopened HIVE-16231:
--------------------------------

This patch is reverted from branch-2 and master due to some to other ideas on how to solve this issue.

> Parquet timestamp may be stored differently since HIVE-12767
> ------------------------------------------------------------
>
>                 Key: HIVE-16231
>                 URL: https://issues.apache.org/jira/browse/HIVE-16231
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Barna Zsombor Klara
>            Assignee: Barna Zsombor Klara
>            Priority: Critical
>         Attachments: HIVE-16231.01.patch, HIVE-16231.02.patch, HIVE-16231.03.patch, HIVE-16231.04.patch
>
>
> If the parquet table is missing its timezone property then the timestamp will be stored with an adjustment instead of without it. This will cause a regression with other applications like Impala or Spark.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)