[
https://issues.apache.org/jira/browse/HIVE-4719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13709502#comment-13709502
]
Phabricator commented on HIVE-4719:
-----------------------------------
ashutoshc has accepted the revision "HIVE-4719 [jira] EmbeddedLockManager
should be shared to all clients".
+1
As Brock pointed out current semantics of just logging the exception in case
of failure to acquire lock (even when Hive is configured to support
concurrency) is not a correct one. We should take this up on follow on.
REVISION DETAIL
https://reviews.facebook.net/D11229
BRANCH
HIVE-4719
ARCANIST PROJECT
hive
To: JIRA, ashutoshc, navis
Cc: brock
> EmbeddedLockManager should be shared to all clients
> ---------------------------------------------------
>
> Key: HIVE-4719
> URL: https://issues.apache.org/jira/browse/HIVE-4719
> Project: Hive
> Issue Type: Bug
> Components: Query Processor
> Reporter: Navis
> Assignee: Navis
> Priority: Trivial
> Attachments: HIVE-4719.D11229.1.patch, HIVE-4719.D11229.2.patch,
> HIVE-4719.D11229.3.patch, HIVE-4719.D11229.4.patch
>
>
> Currently, EmbeddedLockManager is created per Driver instance, so locking has
> no meaning.
--
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
