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

Posted to issues@hive.apache.org by "Eugene Koifman (JIRA)" <ji...@apache.org> on 2015/09/26 04:14:04 UTC

[jira] [Updated] (HIVE-11916) TxnHandler.getOpenTxnsInfo() and getOpenTxns() may produce inconsistent result

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

Eugene Koifman updated HIVE-11916:
----------------------------------
    Attachment: HIVE-11916.patch

> TxnHandler.getOpenTxnsInfo() and getOpenTxns() may produce inconsistent result
> ------------------------------------------------------------------------------
>
>                 Key: HIVE-11916
>                 URL: https://issues.apache.org/jira/browse/HIVE-11916
>             Project: Hive
>          Issue Type: Bug
>          Components: Transactions
>    Affects Versions: 1.0.1
>            Reporter: Eugene Koifman
>            Assignee: Eugene Koifman
>         Attachments: HIVE-11916.patch
>
>
> both run at READ_COMMITTED isolation level and each runs 2 queries.
> Thus it's possible for a new txn to start/commit after hight water mark is recored by these methods.  So the returned list may have txns above the HWM.
> This can be fixed by adding "WHERE TXN_ID < hwm" clause to 2nd query in each case 



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