Return-Path: 
 <user-return-46694-apmail-hbase-user-archive=hbase.apache.org@hbase.apache.org>
X-Original-To: apmail-hbase-user-archive@www.apache.org
Delivered-To: apmail-hbase-user-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 2427B9040
	for <apmail-hbase-user-archive@www.apache.org>;
 Sat, 20 Dec 2014 06:32:27 +0000 (UTC)
Received: (qmail 55156 invoked by uid 500); 20 Dec 2014 06:32:24 -0000
Delivered-To: apmail-hbase-user-archive@hbase.apache.org
Received: (qmail 55080 invoked by uid 500); 20 Dec 2014 06:32:24 -0000
Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@hbase.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@hbase.apache.org>
List-Post: <mailto:user@hbase.apache.org>
List-Id: <user.hbase.apache.org>
Reply-To: user@hbase.apache.org
Delivered-To: mailing list user@hbase.apache.org
Received: (qmail 55032 invoked by uid 99); 20 Dec 2014 06:32:23 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 20 Dec 2014 06:32:23 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of manoj.murumkar@gmail.com
 designates 74.125.82.53 as permitted sender)
Received: from [74.125.82.53] (HELO mail-wg0-f53.google.com) (74.125.82.53)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 20 Dec 2014 06:31:53 +0000
Received: by mail-wg0-f53.google.com with SMTP id l18so2920898wgh.40
        for <user@hbase.apache.org>; Fri, 19 Dec 2014 22:31:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=UtiKYEa+Eb05yEOVhinRvvtEhg5WU4KuM0Z8B+yJchc=;
        b=boRI8dshpLCEhsRiod9hvKBWVj2BgOKCeo1wqIe8lfX2KCwHitoPdGTyT7bLayafC9
         rfQSgHjlRejZFxY64shy4Vkfrkh3CS5YBeSpXskw/cYX+G1aTuaxC8d1ZTxv8U+NmWXz
         a1F5DFJMXG8O/bHxJCBA3wQ0d7I+k50cMY2U5ph3DiSIRcq5HYwtvXJJLVOyqnOrtWkB
         SU391KHkGXNuW12yYMDXNB7k3VjBFcHXs51ZrIt3+GB0V5sm6nCXOx23JimyWcQRpRAN
         j9Ny9m/UrjRCuG3tY4E0OAgPqjmSf7E2AMKprui+VdLRlZ0VWYMkSQssT2zhRyqKGBtt
         V1Cw==
MIME-Version: 1.0
X-Received: by 10.180.78.3 with SMTP id x3mr12344771wiw.82.1419057112376; Fri,
 19 Dec 2014 22:31:52 -0800 (PST)
Received: by 10.27.201.135 with HTTP; Fri, 19 Dec 2014 22:31:52 -0800 (PST)
Date: Fri, 19 Dec 2014 22:31:52 -0800
Message-ID: 
 <CALU28N4qJWe1o+1vxa6cTPPvHzB9SWAsQuvRt7QcGJP-H52UdQ@mail.gmail.com>
Subject: ACLs/Quotas for HBase structures
From: Manoj Murumkar <manoj.murumkar@gmail.com>
To: user@hbase.apache.org
Content-Type: multipart/alternative; boundary=f46d0435c078196ac0050a9ffb1c
X-Virus-Checked: Checked by ClamAV on apache.org

--f46d0435c078196ac0050a9ffb1c
Content-Type: text/plain; charset=UTF-8

Folks,

We are trying to control space usage and manage security at HBase namespace
level. Think of it in terms of a RDBMS (database and superuser for a
database). Is there a simple way to do this?

This is what I have in mind. Does it make sense?


   - Space quotas: Namespace is managed under /apps/hbase/data/data/<namespace>
   directory. We'll  use "dfsadmin -setQuota" to set appropriate quotas.
   - Make <superuser> owner of /apps/hbase/data/data/<namespace> directory
   in hdfs.


Thanks for any pointers from folks who have done this kind of thing.
Appreciate the time.

Manoj

--f46d0435c078196ac0050a9ffb1c--