hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aihua Xu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-10972) DummyTxnManager always locks the current database in shared mode, which is incorrect.
Date Mon, 15 Jun 2015 15:05:00 GMT

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

Aihua Xu commented on HIVE-10972:
---------------------------------

The tests are not related.

> 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
>         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)

Mime
View raw message