Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Tue, 19 Nov 2013 00:49:22 +0000 (UTC)
From: "Owen O'Malley (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: <JIRA.12669392.1379566626172.94837.1384822162332@arcas>
In-Reply-To: <JIRA.12669392.1379566626172@arcas>
References: <JIRA.12669392.1379566626172@arcas>
Subject: [jira] [Commented] (HIVE-5317) Implement insert, update, and delete
 in Hive with full ACID support
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/HIVE-5317?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13826=
009#comment-13826009 ]=20

Owen O'Malley commented on HIVE-5317:
-------------------------------------

Ed,
   If you don't use the insert, update, and delete commands, they won't imp=
act your use of Hive. On the other hand, there are a wide number of users w=
ho need ACID and updates.

> 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 Hiv=
e 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 =E2=80=A6
> * INSERT INTO tbl VALUES ...
> * UPDATE tbl SET =E2=80=A6 WHERE =E2=80=A6
> * DELETE FROM tbl WHERE =E2=80=A6
> * MERGE INTO tbl USING src ON =E2=80=A6 WHEN MATCHED THEN ... WHEN NOT MA=
TCHED THEN ...
> * SET TRANSACTION LEVEL =E2=80=A6
> * BEGIN/END TRANSACTION
> Use Cases
> * Once an hour, a set of inserts and updates (up to 500k rows) for variou=
s dimension tables (eg. customer, inventory, stores) needs to be processed.=
 The dimension tables have primary keys and are typically bucketed and sort=
ed 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 tr=
ansactions are a combination of inserts, updates, and deletes. The table is=
 partitioned and bucketed.


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