hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Barna Zsombor Klara (JIRA)" <>
Subject [jira] [Commented] (HIVE-16469) Parquet timestamp table property is not always taken into account
Date Mon, 08 May 2017 16:50:04 GMT


Barna Zsombor Klara commented on HIVE-16469:

Thanks for the review(s) [~spena], [~Ferd]. I've been struggling with this timestamp fix for
quite some time, so the help is very much appreciated.
The patch is updated on the review board as well if you want to take another look.

> Parquet timestamp table property is not always taken into account
> -----------------------------------------------------------------
>                 Key: HIVE-16469
>                 URL:
>             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,
> 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

View raw message