Return-Path: 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 A8AFD100D4 for ; Sat, 11 Jan 2014 07:59:13 +0000 (UTC) Received: (qmail 19667 invoked by uid 500); 11 Jan 2014 07:59:05 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 19584 invoked by uid 500); 11 Jan 2014 07:59:03 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 19576 invoked by uid 99); 11 Jan 2014 07:59:01 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 11 Jan 2014 07:59:01 +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 takeshi.miao@gmail.com designates 209.85.223.177 as permitted sender) Received: from [209.85.223.177] (HELO mail-ie0-f177.google.com) (209.85.223.177) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 11 Jan 2014 07:58:54 +0000 Received: by mail-ie0-f177.google.com with SMTP id ar20so1953814iec.22 for ; Fri, 10 Jan 2014 23:58:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=+M2UrkSFKp0U4Mse7GYm+/8y02PjFIuZVfpuVbAemXs=; b=RY2DSxbsn5WEo21rcePiZIcusDFV4zYDKQIUmQlUffnAeEvuad2HU1NUsqmf7cuZLR MSGFJ7M52VwR9Fx6sZHB2GW3eJ8PHaJy8Mvusr9F7YrM8973RVjiyrxuOsgC+N5JUopM yA5k1b+d1RQ/lynBnpDQPH6C9bkuvo4FV/GMdyPAG+/Mu1PV45eWmTzolQPeoaKOPiB1 0K9mB10775OKQKu1jjPBvm2F86CjazF4BgX8Wt8X7gjbNRo/BLzLrEdCSKsH30EYXCua eQb6qQR7oIUtaOczMBLlaumjWa7Hc/7OHUylIGDZIx5s5flBW/IDIEkoHRp0oEtB8Ppi NmMw== X-Received: by 10.50.136.201 with SMTP id qc9mr8451113igb.11.1389427113113; Fri, 10 Jan 2014 23:58:33 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.159.39 with HTTP; Fri, 10 Jan 2014 23:58:13 -0800 (PST) In-Reply-To: References: From: takeshi Date: Sat, 11 Jan 2014 15:58:13 +0800 Message-ID: Subject: Re: How to set HBase ACL for groups ? To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=089e01229ed884bf2f04efad3580 X-Virus-Checked: Checked by ClamAV on apache.org --089e01229ed884bf2f04efad3580 Content-Type: text/plain; charset=ISO-8859-1 Hi Gary Your instruction works for us on both 0.99.0 and 0.94.2. BTW, I recommend that the HBase book for the group ACL should doc more details, due to it is important feature for us, so I believe that it might be a important for others as well tks a lot~ Best regards takeshi 2014/1/9 Gary Helmling > To grant privileges to a group, just prefix the group name with '@' in the > grant command. For example, to grant global read/write privileges to the > group "mygroup" in the shell, you would use: > > > grant '@mygroup', 'RW' > > > On Wed, Jan 8, 2014 at 7:59 PM, takeshi wrote: > > > Hi All, > > > > I read following section talking about ACL for group in HBase book > > > 3. HBase managed "roles" as collections of permissions: We will not > model > > "roles" internally in HBase to begin with. We instead allow group names > to > > be granted permissions, which allows external modeling of roles via group > > membership. Groups are created and manipulated externally to HBase, via > the > > Hadoop group mapping service. > > > > So I'd like to try on the *group names to be granted permissions*, how > do I > > do for the settings ? > > > > HBase version: 0.99.0 > > reference: http://hbase.apache.org/book.html#d2907e5580 > > > > Best regards > > > > takeshi > > > --089e01229ed884bf2f04efad3580--