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-16469) Parquet timestamp table property is not always taken into account
Date Mon, 08 May 2017 15:47:04 GMT

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

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

The failing test is known snowflake:
- HIVE-15289

> Parquet timestamp table property is not always taken into account
> -----------------------------------------------------------------
>
>                 Key: HIVE-16469
>                 URL: https://issues.apache.org/jira/browse/HIVE-16469
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Barna Zsombor Klara
>            Assignee: Barna Zsombor Klara
>         Attachments: HIVE-16469.01.patch, HIVE-16469.02.patch, HIVE-16469.03.patch, HIVE-16469.04.patch,
HIVE-16469.05.patch
>
>
> The parquet timestamp timezone property is currently copied over into the JobConf in
the FetchOperator, but this may be too late for some execution paths.
> We should:
> 1 - copy the property over earlier
> 2 - set the default value on the JobConf if no property is set, and fail in the ParquetRecordReader
if the property is missing from the JobConf
> We should add extra validations for the cases when:
> - the property was not set by accident on the JobConf (unexpected execution path)
> - an incorrect/invalid timezone id is being set on the table



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

Mime
View raw message