hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Barna Zsombor Klara (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-16231) Parquet timestamp may be stored differently since HIVE-12767
Date Wed, 22 Mar 2017 11:19:41 GMT

    [ https://issues.apache.org/jira/browse/HIVE-16231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15936136#comment-15936136
] 

Barna Zsombor Klara commented on HIVE-16231:
--------------------------------------------

Failing test is flaky:
- HIVE-16256

> 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
>             Fix For: 2.2.0
>
>         Attachments: HIVE-16231.01.patch, HIVE-16231.02.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.3.15#6346)

Mime
View raw message