hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-15390) Orc reader unnecessarily reading stripe footers with hive.optimize.index.filter set to true
Date Tue, 27 Dec 2016 06:47:58 GMT


Hive QA commented on HIVE-15390:

Here are the results of testing the latest attachment:

{color:red}ERROR:{color} -1 due to no test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 4 failed/errored test(s), 10896 tests executed
*Failed tests:*
TestDerbyConnector - did not produce a TEST-*.xml file (likely timed out) (batchId=234)
org.apache.hadoop.hive.cli.TestMiniLlapCliDriver.testCliDriver[orc_ppd_basic] (batchId=134)
org.apache.hadoop.hive.cli.TestMiniLlapCliDriver.testCliDriver[orc_ppd_schema_evol_3a] (batchId=135)
org.apache.hadoop.hive.cli.TestMiniTezCliDriver.testCliDriver[explainanalyze_5] (batchId=92)

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

This message is automatically generated.

ATTACHMENT ID: 12842473 - PreCommit-HIVE-Build

> Orc reader unnecessarily reading stripe footers with hive.optimize.index.filter set to
> -------------------------------------------------------------------------------------------
>                 Key: HIVE-15390
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: ORC
>    Affects Versions: 1.2.1
>            Reporter: Abhishek Somani
>            Assignee: Abhishek Somani
>         Attachments: HIVE-15390.1.patch, HIVE-15390.patch
> In a split given to a task, the task's orc reader is unnecessarily reading stripe footers
for stripes that are not its responsibility to read. This is happening with hive.optimize.index.filter
set to true.
> Assuming one split per task(no tez grouping considered), a task should not need to read
beyond the split's end offset. Even in some split computation strategies where a split's end
offset can be in the middle of a stripe, it should not need to read more than one stripe beyond
the split's end offset(to fully read a stripe that started in it). However I see that some
tasks make unnecessary filesystem calls to read all the stripe footers in a file from the
split start offset till the end of the file.

This message was sent by Atlassian JIRA

View raw message