hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan Gates (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-13213) make DbLockManger work for non-acid resources
Date Mon, 07 Mar 2016 19:21:40 GMT

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

Alan Gates commented on HIVE-13213:
-----------------------------------

Why is it that insert should get an exclusive lock for non-acid tables?  Two inserts still
can't interfere with each other in any way.  Insert overwrite should certainly get an xlock,
but I believe it already does.

> make DbLockManger work for non-acid resources
> ---------------------------------------------
>
>                 Key: HIVE-13213
>                 URL: https://issues.apache.org/jira/browse/HIVE-13213
>             Project: Hive
>          Issue Type: Bug
>          Components: Transactions
>    Affects Versions: 1.0.0
>            Reporter: Eugene Koifman
>            Assignee: Eugene Koifman
>         Attachments: HIVE-13213.patch
>
>
> for example,
> insert into T values(...)
> if T is an ACID table we acquire Read lock
> but for non-acid table it should acquire Exclusive lock



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message