[ https://issues.apache.org/jira/browse/HBASE-6222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13393360#comment-13393360 ]
Lars George commented on HBASE-6222: ------------------------------------ I am thinking of moving the tags between the key and the value of the KV. The existence would need to be tracked somehow, so we could add a single byte as a bit field to flag the presence. Or add a new type value like PUT_WITH_TAGS or some such. That would leave existing KVs the same and only the code needs to be enhanced to enable the actual security layer - which would be a system level coprocessor I presume. > Add per-KeyValue Security, get federal funding for HBase? > --------------------------------------------------------- > > 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