You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Kelly Stirman (JIRA)" <ji...@apache.org> on 2013/10/15 04:28:42 UTC

[jira] [Commented] (HIVE-5317) Implement insert, update, and delete in Hive with full ACID support

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

Kelly Stirman commented on HIVE-5317:
-------------------------------------

I'm curious - why not use ZK to maintain transactional state.

Hive metastore, if I'm not mistaken, is not HA by default, and it imposes the associated complexity of HA (for MySQL and PG at least) on the user.



> Implement insert, update, and delete in Hive with full ACID support
> -------------------------------------------------------------------
>
>                 Key: HIVE-5317
>                 URL: https://issues.apache.org/jira/browse/HIVE-5317
>             Project: Hive
>          Issue Type: New Feature
>            Reporter: Owen O'Malley
>            Assignee: Owen O'Malley
>         Attachments: InsertUpdatesinHive.pdf
>
>
> Many customers want to be able to insert, update and delete rows from Hive tables with full ACID support. The use cases are varied, but the form of the queries that should be supported are:
> * INSERT INTO tbl SELECT …
> * INSERT INTO tbl VALUES ...
> * UPDATE tbl SET … WHERE …
> * DELETE FROM tbl WHERE …
> * MERGE INTO tbl USING src ON … WHEN MATCHED THEN ... WHEN NOT MATCHED THEN ...
> * SET TRANSACTION LEVEL …
> * BEGIN/END TRANSACTION
> Use Cases
> * Once an hour, a set of inserts and updates (up to 500k rows) for various dimension tables (eg. customer, inventory, stores) needs to be processed. The dimension tables have primary keys and are typically bucketed and sorted on those keys.
> * Once a day a small set (up to 100k rows) of records need to be deleted for regulatory compliance.
> * Once an hour a log of transactions is exported from a RDBS and the fact tables need to be updated (up to 1m rows)  to reflect the new data. The transactions are a combination of inserts, updates, and deletes. The table is partitioned and bucketed.



--
This message was sent by Atlassian JIRA
(v6.1#6144)