hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edward Capriolo (JIRA)" <>
Subject [jira] [Commented] (HIVE-3531) Simple lock manager for dedicated hive server
Date Thu, 04 Oct 2012 17:53:47 GMT


Edward Capriolo commented on HIVE-3531:

[~navis] Interesting.  I do know that the locking does not work well with thrift service currently
as I have had issues with it. 

What is your use case for this? Why would you want a lock manager that does not actually work?
One possibility is that it may be much nicer to make this the default for unit tests, but
other then that I can not think of one.
> Simple lock manager for dedicated hive server
> ---------------------------------------------
>                 Key: HIVE-3531
>                 URL:
>             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:

View raw message