hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enis Soztutar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-5947) Check for valid user/table/family/qualifier and acl state
Date Mon, 11 Jun 2012 18:32:43 GMT

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

Enis Soztutar commented on HBASE-5947:
--------------------------------------

bq. No news on that... check for column qualifier require a deep scan or keeping ref-counted
qualifiers somewhere.
For qualifiers, I think it is fine to not enforce that they exists, but we should check for
table / cf. For preCreateTable, and postDelete, we have to do the scan on ACL table, not on
the actual table, no? 
                
> Check for valid user/table/family/qualifier and acl state
> ---------------------------------------------------------
>
>                 Key: HBASE-5947
>                 URL: https://issues.apache.org/jira/browse/HBASE-5947
>             Project: HBase
>          Issue Type: Sub-task
>          Components: security
>    Affects Versions: 0.92.1, 0.94.0, 0.96.0
>            Reporter: Matteo Bertozzi
>            Assignee: Matteo Bertozzi
>              Labels: acl
>
> HBase Shell grant/revoke doesn't check for valid user or table/family/qualifier so can
you end up having rights for something that doesn't exists.
> We might also want to ensure, upon table/column creation, that no entries are already
stored at the acl table. We might still have residual acl entries if something goes wrong,
in postDeleteTable(), postDeleteColumn().

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message