[
https://issues.apache.org/jira/browse/HIVE-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505315#comment-13505315
]
Phabricator commented on HIVE-3531:
-----------------------------------
navis has closed the revision "HIVE-3531 [jira] Simple lock manager for
dedicated hive server".
Closed by cws.
CHANGED PRIOR TO COMMIT
https://reviews.facebook.net/D5871?vs=22401&id=22593#differential-review-toc
REVISION DETAIL
https://reviews.facebook.net/D5871
COMMIT
https://reviews.facebook.net/rHIVE1414590
To: JIRA, cwsteinbach, navis
> Simple lock manager for dedicated hive server
> ---------------------------------------------
>
> Key: HIVE-3531
> URL: https://issues.apache.org/jira/browse/HIVE-3531
> Project: Hive
> Issue Type: Improvement
> Components: Locking, Server Infrastructure
> Reporter: Navis
> Assignee: Navis
> Priority: Trivial
> Fix For: 0.11
>
> Attachments: HIVE-3531.D5871.1.patch, HIVE-3531.D5871.2.patch,
> HIVE-3531.D5871.3.patch
>
>
> In many cases, we uses hive server as a sole proxy for executing all the
> queries. For that, current default lock manager based on zookeeper seemed a
> little heavy. Simple in-memory lock manager could be enough.
--
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