You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Barna Zsombor Klara (JIRA)" <ji...@apache.org> on 2017/04/18 12:07:42 UTC
[jira] [Created] (HIVE-16469) Parquet timestamp table property is
not always taken into account
Barna Zsombor Klara created HIVE-16469:
------------------------------------------
Summary: 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
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
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)