Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Sat, 16 Jun 2012 20:10:43 +0000 (UTC)
From: "Lars George (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <577122850.22010.1339877443073.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <1104092684.21359.1339824642708.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Commented] (HBASE-6222) Add per-KeyValue Security, get
 federal funding for HBase?
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

I agree with the need of discussing what the objective is and how to get there with the least amount of impact on existing code. That is why I like the idea of reusing the type field. 

I would only add one more type (the one mentioned) and that, together with a global switch, would trigger the code to parse the tags located after the key but before the value (or maybe after the value as it is length prefixed). That tags once parsed can be access then by the coprocessor to do the filtering etc.

So we would need a way to attach tags to a KV as well as access them once they are parsed out. Seems reasonable?
                
> 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