Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 17 Dec 2012 22:42:25 +0000 (UTC)
From: "Andrew Purtell (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12624310.1355763367277.19487.1355784145242@arcas>
In-Reply-To: <JIRA.12624310.1355763367277@arcas>
References: <JIRA.12624310.1355763367277@arcas>
Subject: [jira] [Commented] (HBASE-7367) Snapshot coprocessor and ACL
 security
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/HBASE-7367?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1353=
4389#comment-13534389 ]=20

Andrew Purtell commented on HBASE-7367:
---------------------------------------

I'm also saying that the global admin check is so trivial it seems strange =
if you would not entertain this feedback even on your branch.

bq. my question now is =E2=80=93 if we add the global admin privs checks, w=
ould this be sufficient functionality for when attempting to merge to trunk=
?

In my opinion, yes.=20

I'd want to dig deeper afterward though as a follow up JIRA. Having ACL rec=
onstruction after a clone or restore be a manual task, even if described in=
 detail in the docs, would be a pain. I'd want to see how/if the AccessCont=
roller could cooperate to make that easier.
               =20
> Snapshot coprocessor and ACL security
> -------------------------------------
>
>                 Key: HBASE-7367
>                 URL: https://issues.apache.org/jira/browse/HBASE-7367
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Client, master, regionserver, snapshots, Zookeeper
>            Reporter: Matteo Bertozzi
>            Assignee: Matteo Bertozzi
>            Priority: Minor
>             Fix For: hbase-6055, 0.96.0
>
>         Attachments: HBASE-7367-v0.patch
>
>
> Currently snapshot don't care about ACL...
> and in the first draft snapshots should be disabled if the ACL coprocesso=
r is enabled.
> After the first step, we can discuss how to handle the snapshot/restore/c=
lone.
> Is saving and restoring the _acl_ related rights, the right way? maybe af=
ter 3 months we don't want to give the access the guys listed in the old _a=
cl_...

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira