Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 3C4CC200C0C for ; Mon, 16 Jan 2017 05:59:34 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 3AD3A160B4F; Mon, 16 Jan 2017 04:59:34 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 5DD6C160B32 for ; Mon, 16 Jan 2017 05:59:33 +0100 (CET) Received: (qmail 6467 invoked by uid 500); 16 Jan 2017 04:59:32 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 6456 invoked by uid 99); 16 Jan 2017 04:59:32 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Jan 2017 04:59:32 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id EBD631A05D7 for ; Mon, 16 Jan 2017 04:59:31 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id nb8X05O9d_AS for ; Mon, 16 Jan 2017 04:59:30 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 06B5B5F254 for ; Mon, 16 Jan 2017 04:59:30 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id F0639E0309 for ; Mon, 16 Jan 2017 04:59:28 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 277E424E02 for ; Mon, 16 Jan 2017 04:59:26 +0000 (UTC) Date: Mon, 16 Jan 2017 04:59:26 +0000 (UTC) From: "huzheng (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-17472) Correct the semantic of permission grant MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 16 Jan 2017 04:59:34 -0000 [ https://issues.apache.org/jira/browse/HBASE-17472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huzheng updated HBASE-17472: ---------------------------- Description: Currently, HBase grant operation has following semantic: {code} hbase(main):019:0> grant 'hbase_tst', 'RW', 'ycsb' 0 row(s) in 0.0960 seconds hbase(main):020:0> user_permission 'ycsb' User Namespace,Table,Family,Qualifier:Permission hbase_tst default,ycsb,,: [Permission:actions=READ,WRITE] 4 row(s) in 0.0550 seconds hbase(main):021:0> grant 'hbase_tst', 'CA', 'ycsb' 0 row(s) in 0.0820 seconds hbase(main):022:0> user_permission 'ycsb' User Namespace,Table,Family,Qualifier:Permission hbase_tst default,ycsb,,: [Permission: actions=CREATE,ADMIN] 1 row(s) in 0.0490 seconds {code} Later permission will replace previous granted permissions, It seems confuse most of HBase administrator. It's seems more reasonable that HBase merge multiple granted permission. was: Currently, HBase grant operation has following semantic: {code} hbase(main):019:0> grant 'hbase_tst', 'RW', 'ycsb' 0 row(s) in 0.0960 seconds hbase(main):020:0> user_permission 'ycsb' User Namespace,Table,Family,Qualifier:Permission hbase_tst default,ycsb,,: [Permission:actions=READ,WRITE] 4 row(s) in 0.0550 seconds hbase(main):021:0> grant 'hbase_tst', 'CA', 'ycsb' 0 row(s) in 0.0820 seconds hbase(main):022:0> user_permission 'ycsb' User Namespace,Table,Family,Qualifier:Permission hbase_tst default,ycsb,,: [Permission: actions=CREATE,ADMIN] 1 row(s) in 0.0490 seconds {code} Later permission will replace previous granted permissions seems confuse most of HBase administrator. It's seems more reasonable that HBase merge multiple granted permission. > Correct the semantic of permission grant > ----------------------------------------- > > Key: HBASE-17472 > URL: https://issues.apache.org/jira/browse/HBASE-17472 > Project: HBase > Issue Type: Improvement > Components: Admin > Reporter: huzheng > Assignee: huzheng > > Currently, HBase grant operation has following semantic: > {code} > hbase(main):019:0> grant 'hbase_tst', 'RW', 'ycsb' > 0 row(s) in 0.0960 seconds > hbase(main):020:0> user_permission 'ycsb' > User Namespace,Table,Family,Qualifier:Permission > hbase_tst default,ycsb,,: [Permission:actions=READ,WRITE] > 4 row(s) in 0.0550 seconds > hbase(main):021:0> grant 'hbase_tst', 'CA', 'ycsb' > 0 row(s) in 0.0820 seconds > hbase(main):022:0> user_permission 'ycsb' > User Namespace,Table,Family,Qualifier:Permission > hbase_tst default,ycsb,,: [Permission: actions=CREATE,ADMIN] > 1 row(s) in 0.0490 seconds > {code} > Later permission will replace previous granted permissions, It seems confuse most of HBase administrator. > It's seems more reasonable that HBase merge multiple granted permission. -- This message was sent by Atlassian JIRA (v6.3.4#6332)