[
https://issues.apache.org/jira/browse/HBASE-8358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13634170#comment-13634170
]
Andrew Purtell commented on HBASE-8358:
---------------------------------------
Adding additional permissions to check requires another loop iteration at
minimum for every op, and potentially additional IO (in the case of
HBASE-6222). Internally a delete is another type of write, the put of a
tombstone if you will. A put "overwrites" a given location so in effect
"deletes" the previous value (modulo the number of versions retained according
to schema settings). We should be reluctant to add additional permissions
unless there is a compelling use case or an actual lack in semantics.
> Add delete permission separate from full write permissions
> ----------------------------------------------------------
>
> Key: HBASE-8358
> URL: https://issues.apache.org/jira/browse/HBASE-8358
> Project: HBase
> Issue Type: New Feature
> Reporter: Jeff Kolesky
>
> Currently there are five permissions checked by HBase: read, write, exec,
> create, and admin. An RDBMS allows for more fine-grained control over the
> operations, and it would be helpful to have such controls in HBase.
> Specifically, a distinction between "put" and "delete" would be most useful.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
