hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan Gates (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-7256) HiveTxnManager should be stateless
Date Tue, 24 Jun 2014 21:04:24 GMT

     [ https://issues.apache.org/jira/browse/HIVE-7256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Alan Gates updated HIVE-7256:
-----------------------------

    Attachment: HIVE-7256.patch

This patch creates a new transaction manager and associated lock for HCatalog that extend
DbTxnManager and DbLockManager.  This patch depends on HIVE-7249.

> HiveTxnManager should be stateless
> ----------------------------------
>
>                 Key: HIVE-7256
>                 URL: https://issues.apache.org/jira/browse/HIVE-7256
>             Project: Hive
>          Issue Type: Bug
>          Components: Locking
>    Affects Versions: 0.13.1
>            Reporter: Eugene Koifman
>            Assignee: Alan Gates
>         Attachments: HIVE-7256.patch
>
>
> In order to integrate HCat with Hive ACID, we should be able to create an instance of
HiveTxnManager and use it to acquire locks, and release locks from a different instance of
HiveTxnManager.
> One use case where this shows up is when a job using HCat is retried, since calls to
TxnManager are made from the jobs OutputCommitter.
> Another, is HCatReader/Writer.  For example, TestReaderWriter, calls setupJob()  from
one instance of OutputCommitterContainer and commitJob() from another instance.  The 2nd case
is perhaps better solved by ensuring there is only 1 instance of OutputCommitterContainer.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message