[
https://issues.apache.org/jira/browse/HBASE-6222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13393625#comment-13393625
]
Matt Corgan commented on HBASE-6222:
------------------------------------
{quote}Worth doing a bake-off?{quote}
If we didn't want to wait for the KV interface development to percolate out to
the client code (could take a while), then we'd have to add the tag info to the
current KeyValue via Lars's suggestion or something like it so it can work with
existing mechanisms like the memstore, client, filters, etc. The upside is
that we wouldn't have to be super-paranoid about adding bloat to the KeyValue
since it will someday become just one of the cell implementations. I guess I'm
saying it's maybe ok to muck up the current KV even more given that data block
encoding should be able to clean up the mess down the road. That being said, I
don't personally need this feature so I hate to suggest mucking up anything!
> Add per-KeyValue Security
> -------------------------
>
> Key: HBASE-6222
> URL: https://issues.apache.org/jira/browse/HBASE-6222
> Project: HBase
> Issue Type: New Feature
> Components: security
> Reporter: stack
>
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
