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

Andrew Purtell commented on HBASE-8358:
---------------------------------------

bq. Given how destructive a delete in Hbase can be, and how it is not 
recoverable by just writing the cell back in, I want to be sure that no data 
can be accidentally deleted

HBase already has mechanisms and schema options in place to handle this. I 
don't think it is a security concern per se. You can configure the table with 
KEEP_DELETED_CELLS and then deleted values are retained and are available via 
timerange scans with a "raw scanner", subject to TTL (if set) and MAX_VERSIONS. 
You can also set MIN_VERSIONS, which tells HBase to keep at least MIN_VERSIONS 
versions of a given cell around no matter what, also available via timerange 
scans with a "raw scanner".

bq. Will you point me to the code where the additional loop iteration would 
need to be added so I can understand your performance concerns?

See 
http://svn.apache.org/repos/asf/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/security/access/AccessController.java
 and other classes in that package. There are additional concerns with the 
feature under development on HBASE-6222, specifically the changes proposed for 
AccessController.java, where for cell ACLs we have to go to disk to find 
permissions and we have to then enumerate all permissions found for all 
"covering" KeyValues. Finally, see the last point in the description of 
HBASE-7123. 
                
> 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

Reply via email to