[jira] [Updated] (HIVE-13959) MoveTask should only release its query associated locks

["Chaoyu Tang (JIRA)" <ji...@apache.org>]

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

Chaoyu Tang updated HIVE-13959:
-------------------------------
    Attachment: HIVE-13959.patch

The patch only releases the locks held for MoveTask related query, where the lock was once acquired for this query and in the ctx.getHiveLocks(), so ctx.getHiveLocks().remove(lock) returns true.
Have done manual tests with two Hive debug sessions running two different queries, and verified that one query with MoveTask does not remove the locks acquired for the other query running in other session.


> MoveTask should only release its query associated locks
> -------------------------------------------------------
>
>                 Key: HIVE-13959
>                 URL: https://issues.apache.org/jira/browse/HIVE-13959
>             Project: Hive
>          Issue Type: Bug
>          Components: Locking
>            Reporter: Chaoyu Tang
>            Assignee: Chaoyu Tang
>         Attachments: HIVE-13959.patch
>
>
> releaseLocks in MoveTask releases all locks under a HiveLockObject pathNames. But some of locks under this pathNames might be for other queries and should not be released.



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