You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Lefty Leverenz (JIRA)" <ji...@apache.org> on 2015/04/02 22:43:54 UTC

[jira] [Commented] (HIVE-10200) Add lockId to all ACID log statements

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

Lefty Leverenz commented on HIVE-10200:
---------------------------------------

Hi [~eugene.koifman], some glitch created four identical jiras for this (HIVE-10197 to HIVE-10200).

> Add lockId to all ACID log statements
> -------------------------------------
>
>                 Key: HIVE-10200
>                 URL: https://issues.apache.org/jira/browse/HIVE-10200
>             Project: Hive
>          Issue Type: Bug
>          Components: Transactions
>    Affects Versions: 1.0.0
>            Reporter: Eugene Koifman
>            Assignee: Eugene Koifman
>            Priority: Critical
>
> We should include lockId in all log statements in DbTxnManger, TxnHandler, DbLockManager, etc.  This will make it easier to correlated various logs.



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