[
https://issues.apache.org/jira/browse/HIVE-3533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13471098#comment-13471098
]
Hudson commented on HIVE-3533:
------------------------------
Integrated in Hive-trunk-h0.21 #1726 (See
[https://builds.apache.org/job/Hive-trunk-h0.21/1726/])
HIVE-3533 ZooKeeperHiveLockManager does not respect the option to keep
locks alive even after
the current session has closed (Matt Martin via namit) (Revision 1395026)
Result = SUCCESS
namit : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1395026
Files :
*
/hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/lockmgr/zookeeper/ZooKeeperHiveLockManager.java
> ZooKeeperHiveLockManager does not respect the option to keep locks alive even
> after the current session has closed
> ------------------------------------------------------------------------------------------------------------------
>
> Key: HIVE-3533
> URL: https://issues.apache.org/jira/browse/HIVE-3533
> Project: Hive
> Issue Type: Bug
> Components: Locking
> Affects Versions: 0.9.0
> Reporter: Matt Martin
> Priority: Minor
> Attachments: HIVE-3533.1.patch.txt
>
>
> The HiveLockManager interface defines the following method:
> public List<HiveLock> lock(List<HiveLockObj> objs,
> boolean keepAlive) throws LockException;
> ZooKeeperHiveLockManager implements HiveLockManager, but the current
> implementation of the "lock" method never actually references the "keepAlive"
> parameter. As a result, all of the locks acquired by the "lock" method are
> ephemeral. In other words, Zookeeper-based locks only exist as long as the
> underlying Zookeeper session exists. As soon as the Zookeeper session ends,
> any Zookeeper-based locks are automatically released.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
