Return-Path: X-Original-To: apmail-hive-dev-archive@www.apache.org Delivered-To: apmail-hive-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 98748DA98 for ; Wed, 28 Nov 2012 13:03:08 +0000 (UTC) Received: (qmail 89995 invoked by uid 500); 28 Nov 2012 13:03:06 -0000 Delivered-To: apmail-hive-dev-archive@hive.apache.org Received: (qmail 89853 invoked by uid 500); 28 Nov 2012 13:03:06 -0000 Mailing-List: contact dev-help@hive.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hive.apache.org Delivered-To: mailing list dev@hive.apache.org Received: (qmail 88509 invoked by uid 500); 28 Nov 2012 13:03:00 -0000 Delivered-To: apmail-hadoop-hive-dev@hadoop.apache.org Received: (qmail 88504 invoked by uid 99); 28 Nov 2012 13:03:00 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Nov 2012 13:03:00 +0000 Date: Wed, 28 Nov 2012 13:03:00 +0000 (UTC) From: "Hudson (JIRA)" To: hive-dev@hadoop.apache.org Message-ID: <2067974334.32366.1354107780769.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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HIVE-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505431#comment-13505431 ] Hudson commented on HIVE-3531: ------------------------------ Integrated in Hive-trunk-h0.21 #1822 (See [https://builds.apache.org/job/Hive-trunk-h0.21/1822/]) HIVE-3531 [jira] Simple lock manager for dedicated hive server (Navis Ryu via Carl Steinbach) Summary: DPAL-1906 Implement simple lock manager for hive server 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. Test Plan: TestDedicatedLockManager Reviewers: JIRA, cwsteinbach Reviewed By: cwsteinbach Differential Revision: https://reviews.facebook.net/D5871 (Revision 1414590) Result = ABORTED cws : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1414590 Files : * /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/lockmgr/EmbeddedLockManager.java * /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/lockmgr/HiveLockObject.java * /hive/trunk/ql/src/test/org/apache/hadoop/hive/ql/lockmgr * /hive/trunk/ql/src/test/org/apache/hadoop/hive/ql/lockmgr/TestEmbeddedLockManager.java > 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