hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-5994) ORC RLEv2 decodes wrongly for large negative BIGINTs (64 bits )
Date Tue, 10 Dec 2013 06:57:07 GMT

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

Hive QA commented on HIVE-5994:
-------------------------------



{color:red}Overall{color}: -1 at least one tests failed

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12617962/HIVE-5994.1.patch

{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 4762 tests executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver_decimal_precision
{noformat}

Test results: http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/591/testReport
Console output: http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/591/console

Messages:
{noformat}
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
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12617962

> ORC RLEv2 decodes wrongly for large negative BIGINTs  (64 bits )
> ----------------------------------------------------------------
>
>                 Key: HIVE-5994
>                 URL: https://issues.apache.org/jira/browse/HIVE-5994
>             Project: Hive
>          Issue Type: Bug
>    Affects Versions: 0.13.0
>            Reporter: Prasanth J
>            Assignee: Prasanth J
>              Labels: orcfile
>         Attachments: HIVE-5994.1.patch
>
>
> For large negative BIGINTs, zigzag encoding will yield large value (64bit value) with
MSB set to 1. This value is interpreted as negative value in SerializationUtils.findClosestNumBits(long
value) function. This resulted in wrong computation of total number of bits required which
results in wrong encoding/decoding of values.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

Mime
View raw message