You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hive.apache.org by "Eugene Koifman (JIRA)" <ji...@apache.org> on 2017/08/02 19:15:01 UTC

[jira] [Created] (HIVE-17231) ColumnizedDeleteEventRegistry.DeleteReaderValue optimization

Eugene Koifman created HIVE-17231:
-------------------------------------

             Summary: 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


     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.




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)