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

Lars George commented on HBASE-6222:
------------------------------------

bq. @Lars When you say "...I thought it might be good to have the option to add 
"tags" to each KV", what would a tag look like? A bit set? Or some name/values 
within the KV?

I would assume the latter, a map of key values for each tag. 

Please note that I would like for these tags NOT just being used for security, 
but also as something we can use in a broader sense. Like the per KV memstoreTS 
idea. They can be optionally attached to the KVs when needed. The approach does 
not change the existing KVs nor any comparator code. Maybe the above is not a 
good example as that seems something that is eventually needed for all KVs and 
would warrant for a more tighten terrain into the key and comparators. But I am 
hoping you get the idea?

So far the other approaches (if discussed on that level yet at all) are trying 
to store the security in collateral places, which I think is not good enough to 
be compared with Accumulo. But I might be wrong. I personally think that having 
the ACLs outside the KV asks for situations where the info is lost. I think the 
data is so important, it should be part of the KV itself. Just thinking out 
loud. 
                
> 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

        

Reply via email to