[
https://issues.apache.org/jira/browse/HBASE-6222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13585714#comment-13585714
]
ramkrishna.s.vasudevan commented on HBASE-6222:
-----------------------------------------------
Andy,
The memstore flushes if more than 1 CF exists, will it have an impact on this
new CF introduced?
One more question is,
Once in the AccessController hooks we have ensured that the permission is
available by checking the new CF _acl_, when the actual scan goes we can avoid
this Cell right? May be am missing something. Pls correct me if am wrong.
> Add per-KeyValue Security
> -------------------------
>
> Key: HBASE-6222
> URL: https://issues.apache.org/jira/browse/HBASE-6222
> Project: HBase
> Issue Type: New Feature
> Components: security
> Affects Versions: 0.96.0, 0.98.0
> Reporter: stack
> Assignee: Andrew Purtell
> Attachments: 6222-aclcf.patch, 6222.pdf,
> cell-acls-kv-tags-not-for-review.zip,
> HBaseCellRow-LevelSecurityDesignDoc.docx, HBaseCellRow-LevelSecurityPRD.docx
>
>
> Saw an interesting article:
> http://www.fiercegovernmentit.com/story/sasc-accumulo-language-pro-open-source-say-proponents/2012-06-14
> "The Senate Armed Services Committee version of the fiscal 2013 national
> defense authorization act (S. 3254) would require DoD agencies to foreswear
> the Accumulo NoSQL database after Sept. 30, 2013, unless the DoD CIO
> certifies that there exists either no viable commercial open source database
> with security features comparable to [Accumulo] (such as the HBase or
> Cassandra databases)..."
> Not sure what a 'commercial open source database' is, and I'm not sure whats
> going on in the article, but tra-la-la'ing, if we had per-KeyValue 'security'
> like Accumulo's, we might put ourselves in the running for federal
> contributions?
--
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
