hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Duo Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-11013) Clone Snapshots on Secure Cluster Should provide option to apply Retained User Permissions
Date Wed, 17 May 2017 02:05:04 GMT

    [ https://issues.apache.org/jira/browse/HBASE-11013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16013401#comment-16013401

Duo Zhang commented on HBASE-11013:


I think the most important thing is the API that provided to user. At the user side, it does
not make any differences whether we implement AccessController using CP or not, we are free
to change it at any time. But AccessControlClient is a public API, and it uses the endpoint
API to connect to AccessController, this is what I want to eliminate here. Maybe we can move
the API to master?

OK the issue is HBASE-16757. Let's discuss there.

> 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.branch-1.1.v1.patch, HBASE-11013.branch-1.2.v1.patch,
HBASE-11013.branch-1.3.v1.patch, HBASE-11013.branch-1.v1.patch, HBASE-11013.master.addendum.patch,
HBASE-11013.v1.patch, HBASE-11013.v2.patch, HBASE-11013.v3.patch, HBASE-11013.v4.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
> 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

View raw message