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

Posted to issues@hive.apache.org by "Chaoyu Tang (JIRA)" <ji...@apache.org> on 2015/06/20 22:35:00 UTC

[jira] [Resolved] (HIVE-10972) DummyTxnManager always locks the current database in shared mode, which is incorrect.

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

Chaoyu Tang resolved HIVE-10972.
--------------------------------
       Resolution: Fixed
    Fix Version/s: 2.0.0
                   1.3.0

Committed to Hive 2.0.0 and 1.3.0. Thanks [~aihuaxu] for the patch and [~alangates] for review.

> DummyTxnManager always locks the current database in shared mode, which is incorrect.
> -------------------------------------------------------------------------------------
>
>                 Key: HIVE-10972
>                 URL: https://issues.apache.org/jira/browse/HIVE-10972
>             Project: Hive
>          Issue Type: Bug
>          Components: Locking
>    Affects Versions: 2.0.0
>            Reporter: Aihua Xu
>            Assignee: Aihua Xu
>             Fix For: 1.3.0, 2.0.0
>
>         Attachments: HIVE-10972.2.patch, HIVE-10972.patch
>
>
> In DummyTxnManager [line 163 | http://grepcode.com/file/repo1.maven.org/maven2/co.cask.cdap/hive-exec/0.13.0/org/apache/hadoop/hive/ql/lockmgr/DummyTxnManager.java#163], it always locks the current database. 
> That is not correct since the current database can be "db1", and the query can be "select * from db2.tb1", which will lock db1 unnecessarily.



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