hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Shelukhin (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HIVE-18570) ACID IOW implemented using base may delete too much data
Date Mon, 29 Jan 2018 19:43:00 GMT
Sergey Shelukhin created HIVE-18570:
---------------------------------------

             Summary: ACID IOW implemented using base may delete too much data
                 Key: HIVE-18570
                 URL: https://issues.apache.org/jira/browse/HIVE-18570
             Project: Hive
          Issue Type: Bug
            Reporter: Sergey Shelukhin


Suppose we have a table with delta_0 insert data.
Txn 1 starts an insert into delta_1.
Txn 2 starts an IOW into base_2.
Txn 2 commits.
Txn 1 commits after txn 2 but its results would be invisible.

If we treat IOW foo like DELETE FROM foo (to reason about it w.r.t. ACID semantics), it seems
to me this sequence of events is only possible under read-uncommitted isolation level (so,
2 deletes rows written by 1).
Under any other isolation level rows written by 1 must survive, or there must be some lock
based change in sequence or conflict.







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

Mime
View raw message