[
https://issues.apache.org/jira/browse/HIVE-25638?focusedWorklogId=672008&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-672008
]
ASF GitHub Bot logged work on HIVE-25638:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 29/Oct/21 15:09
Start Date: 29/Oct/21 15:09
Worklog Time Spent: 10m
Work Description: maheshk114 merged pull request #2747:
URL: https://github.com/apache/hive/pull/2747
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 672008)
Time Spent: 20m (was: 10m)
> Select returns deleted records in Hive ACID table
> -------------------------------------------------
>
> Key: HIVE-25638
> URL: https://issues.apache.org/jira/browse/HIVE-25638
> Project: Hive
> Issue Type: Bug
> Components: HiveServer2
> Reporter: mahesh kumar behera
> Assignee: mahesh kumar behera
> Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Hive stores the stripe stats in the ORC files. During select, these stats are
> used to create the SARG. The SARG is used to reduce the records read from the
> delete-delta files. Currently, in case where the number of stripes are more
> than 1, the SARG generated is not proper as it uses the first stripe index
> for both min and max key interval. The max key interval should be obtained
> from last stripe index. This cause some valid deleted records to be skipped.
> And those records are return to the user. We need the last stripe here
> instead of the first one, is the fact the keys are ordered in the file.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
