hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eugene Koifman (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-17231) ColumnizedDeleteEventRegistry.DeleteReaderValue optimization
Date Fri, 12 Oct 2018 23:36:00 GMT

    [ https://issues.apache.org/jira/browse/HIVE-17231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16648583#comment-16648583
] 

Eugene Koifman commented on HIVE-17231:
---------------------------------------

[~gopalv] could you review please?

> ColumnizedDeleteEventRegistry.DeleteReaderValue optimization
> ------------------------------------------------------------
>
>                 Key: HIVE-17231
>                 URL: https://issues.apache.org/jira/browse/HIVE-17231
>             Project: Hive
>          Issue Type: Sub-task
>          Components: Transactions
>            Reporter: Eugene Koifman
>            Assignee: Eugene Koifman
>            Priority: Major
>         Attachments: HIVE-17231.01.patch, HIVE-17231.02.patch
>
>
>      For unbucketed tables DeleteReaderValue will currently return all delete events.
 Once we trust that
>      the N in bucketN for "base" spit is reliable, all delete events not matching N can
be skipped.
> This is useful to protect against extreme cases where someone runs an update/delete on
a partition that matches 10 billion rows thus generates very many delete events.
> Since HIVE-19890 all acid data files must have bucketid/writerid in the file name match
bucketid/writerid in ROW__ID in the data.
> {{OrcRawRecrodMerger.getDeltaFiles()}} should only return files representing the right
{{bucket}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message