[
https://issues.apache.org/jira/browse/HBASE-12592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14227537#comment-14227537
]
Matteo Bertozzi commented on HBASE-12592:
-----------------------------------------
once we will have a proper notification bus, the truncate can be implemented as
notification to the regions to delete all the files.
at the moment we just have a workaround drop/recreate. The reason we introduced
a truncate was to do a "clear" of the table but avoiding to delete every single
record and also to be able to perform the "clear" operation as a table admin
(drop & create requires a global permission)
> Fix the truncate feature or purge it.
> -------------------------------------
>
> Key: HBASE-12592
> URL: https://issues.apache.org/jira/browse/HBASE-12592
> Project: HBase
> Issue Type: Umbrella
> Reporter: stack
> Assignee: stack
>
> While working on our move to unmanaged connections, I ran into issues in
> TestAccessController.testTruncatePerms; the acl permissions were not being
> restored when the table was restored. Digging, I ended up in the truncate
> 'handler'. Its a subclass of the delete table handler. For the create table
> part of trunctate, it does not call create table handler. Instead it
> copy/pastes what is going on over there only the copy/paste has rotted and
> needs recalibrating so acl perms get restored at least; better would be
> removing the copy/paste and using the create table handler. Or, we could
> just drop the truncate feature as just not appropriate to a store like this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
