Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Fri, 5 Oct 2012 05:01:48 +1100 (NCT)
From: "Edward Capriolo (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: <1333414333.988.1349373708426.JavaMail.jiratomcat@arcas>
In-Reply-To: <1628226226.164113.1349333107685.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (HIVE-3531) Simple lock manager for dedicated
 hive server
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HIVE-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13469558#comment-13469558 ] 

Edward Capriolo commented on HIVE-3531:
---------------------------------------

@Carl Why? See my comments above. I am worried about code bloat in hive (No offense Navis your code is great). What is the case for having a lock manager that only does half the things a lock manager is supposed to do?
                
> 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