You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Jason Dere (Jira)" <ji...@apache.org> on 2019/12/03 23:02:00 UTC
[jira] [Commented] (HIVE-20801) ACID: Allow DbTxnManager to ignore
non-ACID table locking
[ https://issues.apache.org/jira/browse/HIVE-20801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16987340#comment-16987340 ]
Jason Dere commented on HIVE-20801:
-----------------------------------
Is anything going on with this Jira? I am +1 on this one, especially considering that on Apache Hive there is still the ability to have non-transactional managed tables.
> ACID: Allow DbTxnManager to ignore non-ACID table locking
> ---------------------------------------------------------
>
> Key: HIVE-20801
> URL: https://issues.apache.org/jira/browse/HIVE-20801
> Project: Hive
> Issue Type: Bug
> Components: Locking, Transactions
> Affects Versions: 4.0.0
> Reporter: Gopal Vijayaraghavan
> Assignee: Gopal V
> Priority: Major
> Labels: Branch3Candidate, TODOC
> Attachments: HIVE-20801.1.patch, HIVE-20801.2.patch, HIVE-20801.2.patch, HIVE-20801.3.patch, HIVE-20801.3.patch
>
>
> Enabling ACIDv1 on a cluster produces a central locking bottleneck for all table types, which is not always the intention.
> The Hive locking for non-acid tables are advisory (i.e a client can write/read without locking), which means that the implementation does not offer strong consistency despite the lock manager consuming resources centrally.
> Disabling this lock acquisition would improve the performance of non-ACID tables co-existing with a globally configured DbTxnManager implementation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)