hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-7239) Fix bug in HiveIndexedInputFormat implementation that causes incorrect query result when input backed by Sequence/RC files
Date Thu, 28 Jul 2016 16:33:20 GMT


Hive QA commented on HIVE-7239:

Here are the results of testing the latest attachment:

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

{color:red}ERROR:{color} -1 due to 5 failed/errored test(s), 10391 tests executed
*Failed tests:*
TestMsgBusConnection - did not produce a TEST-*.xml file

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: 5 tests failed

This message is automatically generated.

ATTACHMENT ID: 12820366 - PreCommit-HIVE-MASTER-Build

> Fix bug in HiveIndexedInputFormat implementation that causes incorrect query result when
input backed by Sequence/RC files
> --------------------------------------------------------------------------------------------------------------------------
>                 Key: HIVE-7239
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: Indexing
>    Affects Versions: 2.1.0
>            Reporter: Sumit Kumar
>            Assignee: Illya Yalovyy
>         Attachments: HIVE-7239.2.patch, HIVE-7239.3.patch, HIVE-7239.4.patch, HIVE-7239.patch
> In case of sequence files, it's crucial that splits are calculated around the boundaries
enforced by the input sequence file. However by default hadoop creates input splits depending
on the configuration parameters which may not match the boundaries for the input sequence
file. Hive provides HiveIndexedInputFormat that provides extra logic and recalculates the
split boundaries for each split depending on the sequence file's boundaries.
> However we noticed this behavior of "over" reporting from data backed by sequence file.
We've a sample data on which we experimented and fixed this bug, we have verified this fix
by comparing the query output for input being sequence file format, rc file and regular format.
However we have not able to find the right place to include this as a unit test that would
execute as part of hive tests. We tried writing a "clientpositive" test as part of ql module
but the output seems quite verbose and i couldn't interpret it that well. Can someone please
review this change and guide on how to write a test that will execute as part of Hive testing?

This message was sent by Atlassian JIRA

View raw message