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

Vandana Ayyalasomayajula commented on HBASE-12142:
--------------------------------------------------

[~tedyu] yes, the change is intentional, for the two reasons, (1) once a table 
is created, we grant all "RWXCA" perms to the user who created it. So I think 
its fair to assume that in most of the cases, a user who wants to truncate a 
table will be its admin, (2) To read acls of a table, the user need to be admin.

[~mbertozzi] Yes, thats a valid point that we don't have a failure event. I 
used a weak hash map, so that the objects are collected by GC, if they remain 
long enough.  

> Truncate command does not preserve ACLs table
> ---------------------------------------------
>
>                 Key: HBASE-12142
>                 URL: https://issues.apache.org/jira/browse/HBASE-12142
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.98.6
>            Reporter: Vandana Ayyalasomayajula
>            Assignee: Vandana Ayyalasomayajula
>            Priority: Minor
>              Labels: security
>         Attachments: HBASE-12142_0.patch
>
>
> The current truncate command does not preserve acls on a table. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to