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] [Updated] (HIVE-10984) "Lock table" explicit lock command doesn't lock the database object.
Date Mon, 15 Jun 2015 19:37:00 GMT

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

Aihua Xu updated HIVE-10984:
----------------------------
    Summary: "Lock table" explicit lock command doesn't lock the database object.  (was: When
ZooKeeperHiveLockManager locks an object exclusively, it doesn't check the lock on the children.)

> "Lock table" explicit lock command doesn't lock the database object.
> --------------------------------------------------------------------
>
>                 Key: HIVE-10984
>                 URL: https://issues.apache.org/jira/browse/HIVE-10984
>             Project: Hive
>          Issue Type: Bug
>          Components: Locking
>            Reporter: Aihua Xu
>            Assignee: Aihua Xu
>
> There is an issue in ZooKeeperHiveLockManager.java, in which when locking exclusively
on an object we didn't check if the children are locked.
> So the following should not be allowed.
> {noformat}
> use default; 
> lock table lockneg2.tstsrcpart shared; 
> lock database lockneg2 exclusive;
> {noformat}
> Also check the test case lockneg_try_lock_db_in_use.q to add more reasonable failure
cases.



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

Mime
View raw message