[
https://issues.apache.org/jira/browse/HIVE-13213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183615#comment-15183615
]
Eugene Koifman commented on HIVE-13213:
---------------------------------------
That is the behavior documented previously in
https://cwiki.apache.org/confluence/display/Hive/Locking. W/o this, if users
enable ACID but continue to run their existing workflows with non-acid
resources they end up with with different semantics than before and they have
no way to get those semantics back except to disable acid.
> 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)
