hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-16469) Parquet timestamp table property is not always taken into account
Date Sun, 07 May 2017 08:35:04 GMT


Hive QA commented on HIVE-16469:

Here are the results of testing the latest attachment:

{color:green}SUCCESS:{color} +1 due to 7 test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 10642 tests executed
*Failed tests:*

Test results:
Console output:
Test logs:

Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 1 tests failed

This message is automatically generated.

ATTACHMENT ID: 12866753 - PreCommit-HIVE-Build

> 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