[
https://issues.apache.org/jira/browse/HBASE-6222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13393618#comment-13393618
]
Andrew Purtell commented on HBASE-6222:
---------------------------------------
@Matt
{quote}
bq. @Matt So attributes carry in information and we use a new encoding type to
store tags adjacent to KVs if they are labelled?
Yeah, basically you would be required to use the new encoding format
(TaggedPrefixTrie, for example), and if you switched back to
DataBlockEncoding.NONE, your tags would be erased (we'd want to make that
scenario appropriately difficult of course.). The trie would de-duplicate them,
take up no space if they aren't there, and use >=1 byte per cell index if they
are there.
{quote}
So we may have this as a way to store tags inline with data, with
dedup/optimize away if not needed; and we may have Lars' somehow tag structure
addition to KV (Lars: what would that look like?). Worth doing a bake-off?
> 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
