[jira] [Updated] (HIVE-10984) When ZooKeeperHiveLockManager locks an object exclusively, it doesn't check the lock on the children.

["Aihua Xu (JIRA)" <ji...@apache.org>]

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

Aihua Xu updated HIVE-10984:
----------------------------
    Description: 
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.

  was:
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}


> When ZooKeeperHiveLockManager locks an object exclusively, it doesn't check the lock on the children.
> -----------------------------------------------------------------------------------------------------
>
>                 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)