You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Wei Zheng (JIRA)" <ji...@apache.org> on 2017/02/02 22:40:51 UTC

[jira] [Comment Edited] (HIVE-15774) Ensure DbLockManager backward compatibility for non-ACID resources

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

Wei Zheng edited comment on HIVE-15774 at 2/2/17 10:40 PM:
-----------------------------------------------------------

Wiki doc updated:
https://cwiki.apache.org/confluence/display/Hive/Configuration+Properties#ConfigurationProperties-Transactions
https://cwiki.apache.org/confluence/display/Hive/Hive+Transactions#HiveTransactions-NewConfigurationParametersforTransactions


was (Author: wzheng):
Wiki doc updated: https://cwiki.apache.org/confluence/display/Hive/Configuration+Properties#ConfigurationProperties-Transactions

> Ensure DbLockManager backward compatibility for non-ACID resources
> ------------------------------------------------------------------
>
>                 Key: HIVE-15774
>                 URL: https://issues.apache.org/jira/browse/HIVE-15774
>             Project: Hive
>          Issue Type: Improvement
>          Components: Hive, Transactions
>            Reporter: Wei Zheng
>            Assignee: Wei Zheng
>             Fix For: 2.2.0
>
>         Attachments: HIVE-15774.1.patch, HIVE-15774.2.patch, HIVE-15774.3.patch
>
>
> In pre-ACID days, users perform operations such as INSERT with either ZooKeeperHiveLockManager or no lock manager at all. If their workflow is designed to take advantage of no locking and they take care of the control of concurrency, this works well with good performance.
> With ACID, if users enable transactions (i.e. using DbTxnManager & DbLockManager), then for all the operations, different types of locks will be acquired accordingly by DbLockManager, even for non-ACID resources. This may impact the performance of some workflows designed for pre-ACID use cases.
> A viable solution would be to differentiate the locking mode for ACID and non-ACID resources, so that DbLockManager will continue its current behavior for ACID tables, but will be able to acquire a less strict lock type for non-ACID resources, thus avoiding the performance loss for those workflows.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)