[
https://issues.apache.org/jira/browse/HBASE-6222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13393621#comment-13393621
]
Andrew Purtell commented on HBASE-6222:
---------------------------------------
bq. All-in-all, the tags raise some interesting questions in my mind like "why
isn't everything in the KV implemented as a tag?" For example, i'd love to see
per-cell TTL's someday. Maybe tags go hand-in-hand with co-processors to
implement features like that?
The metacolumn idea was actually the result of some brainstorming on how to do
per-cell TTLs. By no means do I raise it as a potentially superior alternative,
simply one implementation strategy that wouldn't touch core. However tags in KV
would be another way to go that touches core only once.
We could agree on criteria such as:
* Tag storage optimized out if no tags present
* Compartmentalized changes
* Generic mechanism for adding, reading, removing, and modifying tags, usable
by coprocessors.
maybe?
> 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
