You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hive.apache.org by "Phabricator (JIRA)" <ji...@apache.org> on 2013/03/12 04:25:13 UTC

[jira] [Updated] (HIVE-4152) Lock owner should be allowed to acquire lock again on EmbeddedLockManager

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

Phabricator updated HIVE-4152:
------------------------------

    Attachment: HIVE-4152.D9303.1.patch

navis requested code review of "HIVE-4152 [jira] Lock owner should be allowed to acquire lock again on EmbeddedLockManager".

Reviewers: JIRA

HIVE-4152 Lock owner should be allowed to acquire lock again on EmbeddedLockManager

If a query owns lock on a path, it should be allowed to acquire lock on it again with success. Current EmbeddedLockManager returns null in this situation and makes some query to wait infinitely.

TEST PLAN
  EMPTY

REVISION DETAIL
  https://reviews.facebook.net/D9303

AFFECTED FILES
  common/src/java/org/apache/hadoop/hive/conf/HiveConf.java
  conf/hive-default.xml.template
  ql/src/java/org/apache/hadoop/hive/ql/lockmgr/EmbeddedLockManager.java
  ql/src/java/org/apache/hadoop/hive/ql/lockmgr/HiveLockObject.java
  ql/src/test/org/apache/hadoop/hive/ql/lockmgr/TestEmbeddedLockManager.java

MANAGE HERALD RULES
  https://reviews.facebook.net/herald/view/differential/

WHY DID I GET THIS EMAIL?
  https://reviews.facebook.net/herald/transcript/22395/

To: JIRA, navis

                
> Lock owner should be allowed to acquire lock again on EmbeddedLockManager
> -------------------------------------------------------------------------
>
>                 Key: HIVE-4152
>                 URL: https://issues.apache.org/jira/browse/HIVE-4152
>             Project: Hive
>          Issue Type: Bug
>          Components: Locking
>            Reporter: Navis
>            Assignee: Navis
>            Priority: Trivial
>         Attachments: HIVE-4152.D9303.1.patch
>
>
> If a query owns lock on a path, it should be allowed to acquire lock on it again with success. Current EmbeddedLockManager returns null in this situation and makes some query to wait infinitely.

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