[
https://issues.apache.org/jira/browse/HIVE-19838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Shelukhin updated HIVE-19838:
------------------------------------
Description:
Apparently sometimes the delete count in ACID stats doesn't match what merger
actually returns.
It could be due to some deltas having duplicate deletes from parallel queries
(I guess?) that are being squashed by the merger or some other reasons beyond
my mortal comprehension.
The loop assumes the merger will return the exact number of records, so it
fails with array index exception. Also, it could actually be done in a single
loop.
was:
Apparently sometimes the delete count in ACID stats doesn't match what merger
actually returns.
It could be due to some deltas having duplicate deletes from parallel queries
(I guess?) or some other reasons beyond my mortal comprehension.
The loop assumes the merger will return the exact number of records, so it
fails with array index exception. Also, it could actually be done in a single
loop.
> simplify & fix ColumnizedDeleteEventRegistry load loop
> ------------------------------------------------------
>
> Key: HIVE-19838
> URL: https://issues.apache.org/jira/browse/HIVE-19838
> Project: Hive
> Issue Type: Bug
> Reporter: Sergey Shelukhin
> Assignee: Sergey Shelukhin
> Priority: Major
>
> Apparently sometimes the delete count in ACID stats doesn't match what merger
> actually returns.
> It could be due to some deltas having duplicate deletes from parallel queries
> (I guess?) that are being squashed by the merger or some other reasons beyond
> my mortal comprehension.
> The loop assumes the merger will return the exact number of records, so it
> fails with array index exception. Also, it could actually be done in a single
> loop.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
