[
https://issues.apache.org/jira/browse/HIVE-6656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13937342#comment-13937342
]
Hive QA commented on HIVE-6656:
-------------------------------
{color:green}Overall{color}: +1 all checks pass
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12634959/HIVE-6656.1.patch.txt
{color:green}SUCCESS:{color} +1 5408 tests passed
Test results:
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/1853/testReport
Console output:
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/1853/console
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12634959
> Bug in ORC Timestamp reader returns wrong nanoseconds
> -----------------------------------------------------
>
> Key: HIVE-6656
> URL: https://issues.apache.org/jira/browse/HIVE-6656
> Project: Hive
> Issue Type: Bug
> Affects Versions: 0.13.0, 0.14.0
> Reporter: Prasanth J
> Assignee: Prasanth J
> Labels: orcfile
> Attachments: HIVE-6656.1.patch, HIVE-6656.1.patch.txt
>
>
> ORC timestamp writer stores the number of trailing zeros in 3 LSB bits. There
> is a bug in parsing nanosecond logic that returns incorrect value.
> Input:
> 1999-01-01 00:00:00.999999999
> Output:
> 1999-01-01 00:00:00.463129087
> The fix for this is parseNanos() should first right shift by 3 and then
> typecast to int.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
