hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-21460) ACID: Load data followed by a select * query results in incorrect results
Date Tue, 19 Mar 2019 13:52:00 GMT


Hive QA commented on HIVE-21460:

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 2 failed/errored test(s), 15833 tests executed
*Failed tests:*
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[vector_groupby_reduce] (batchId=61)
org.apache.hadoop.hive.cli.TestNegativeCliDriver.testCliDriver[udaf_invalid_place] (batchId=99)

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.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 2 tests failed

This message is automatically generated.

ATTACHMENT ID: 12962943 - PreCommit-HIVE-Build

> ACID: Load data followed by a select * query results in incorrect results
> -------------------------------------------------------------------------
>                 Key: HIVE-21460
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: Transactions
>    Affects Versions: 4.0.0, 3.1.1
>            Reporter: Vaibhav Gumashta
>            Assignee: Vaibhav Gumashta
>            Priority: Blocker
>         Attachments: HIVE-21460.1.patch
> This affects current master as well. Created an orc file such that it spans multiple
stripes and ran a simple select *, and got incorrect row counts (when comparing with select
count(*). The problem seems to be that after split generation and creating min/max rowId for
each row (note that since the loaded file is not written by Hive ACID, it does not have ROW__ID
in the file; but the ROW__ID is applied on read by discovering min/max bounds which are used
for calculating ROW__ID.rowId for each row of a split), Hive is only reading the last split.

This message was sent by Atlassian JIRA

View raw message