[
https://issues.apache.org/jira/browse/HIVE-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13469857#comment-13469857
]
Navis commented on HIVE-3531:
-----------------------------
@Edward: As stated in description, we delegates execution of all the queries to
a single hive server. In this case, external lock manager like a zookeeper
could be used but it's not required thing. But it does not mean locking itself
is not needed. Multiple queries could be executed concurrently and still need a
appropriate locking system.
I didn't think of locking mechanism of hive deeply yet. It's just in-memory
version of zookeeper lock manager. The part "locking does not working well" in
your comment should be an another issue.
> 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: Server Infrastructure
> Reporter: Navis
> Assignee: Navis
> Priority: Trivial
> Attachments: HIVE-3531.D5871.1.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
