You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Vaibhav Gumashta (JIRA)" <ji...@apache.org> on 2019/04/01 18:03:00 UTC
[jira] [Updated] (HIVE-21460) ACID: Load data followed by a select
* query results in incorrect results
[ https://issues.apache.org/jira/browse/HIVE-21460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vaibhav Gumashta updated HIVE-21460:
------------------------------------
Reporter: Brian Goerlitz (was: Vaibhav Gumashta)
> ACID: Load data followed by a select * query results in incorrect results
> -------------------------------------------------------------------------
>
> Key: HIVE-21460
> URL: https://issues.apache.org/jira/browse/HIVE-21460
> Project: Hive
> Issue Type: Bug
> Components: Transactions
> Affects Versions: 4.0.0, 3.1.1
> Reporter: Brian Goerlitz
> Assignee: Vaibhav Gumashta
> Priority: Blocker
> Fix For: 4.0.0, 3.1.1
>
> 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
(v7.6.3#76005)