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 98B8F200C63 for ; Thu, 11 May 2017 12:31:12 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 975BA160BB2; Thu, 11 May 2017 10:31:12 +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 DDFA0160BC7 for ; Thu, 11 May 2017 12:31:11 +0200 (CEST) Received: (qmail 96234 invoked by uid 500); 11 May 2017 10:31:10 -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 96084 invoked by uid 99); 11 May 2017 10:31:10 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 May 2017 10:31:10 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id E3612CA6D9 for ; Thu, 11 May 2017 10:31:09 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id YZVo5qrJbxnw for ; Thu, 11 May 2017 10:31:09 +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 9A2425FDCB for ; Thu, 11 May 2017 10:31:06 +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 AC35EE02C7 for ; Thu, 11 May 2017 10:31:05 +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 3D2D921E14 for ; Thu, 11 May 2017 10:31:04 +0000 (UTC) Date: Thu, 11 May 2017 10:31:04 +0000 (UTC) From: "Duo Zhang (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-11013) Clone Snapshots on Secure Cluster Should provide option to apply Retained User Permissions MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 11 May 2017 10:31:12 -0000 [ https://issues.apache.org/jira/browse/HBASE-11013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16006213#comment-16006213 ] Duo Zhang commented on HBASE-11013: ----------------------------------- [~stack] Sir, seems AccessControl.proto and Authentication.proto are only in hbase-protocol module. Is there any reason that we do not shade them in hbase-protocol-shaded module? Thanks. > Clone Snapshots on Secure Cluster Should provide option to apply Retained User Permissions > ------------------------------------------------------------------------------------------ > > Key: HBASE-11013 > URL: https://issues.apache.org/jira/browse/HBASE-11013 > Project: HBase > Issue Type: Improvement > Components: snapshots > Reporter: Ted Yu > Assignee: Zheng Hu > Fix For: 2.0.0 > > Attachments: HBASE-11013.v1.patch, HBASE-11013.v2.patch > > > Currently, > {code} > sudo su - test_user > create 't1', 'f1' > sudo su - hbase > snapshot 't1', 'snap_one' > clone_snapshot 'snap_one', 't2' > {code} > In this scenario the user - test_user would not have permissions for the clone table t2. > We need to add improvement feature such that the permissions of the original table are recorded in snapshot metadata and an option is provided for applying them to the new table as part of the clone process. -- This message was sent by Atlassian JIRA (v6.3.15#6346)