hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars George (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6222) Add per-KeyValue Security
Date Sun, 17 Jun 2012 08:19:42 GMT

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

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

bq.  If we add a ColumnVisibility-like expression into the KV, we'd have to update Comparators
to exclude this portion from inclusion in sort.

That is the whole point of my proposal up top, using the new type and attaching the tag bag
*after* the key, the default code path stays untouched. 

Sure this needs some extra conditional statements, but is easy to test for. The rest of the
tests need no overhaul. All the other approaches strike me as overkill - although they might
be worthwhile in their own right. So the question is, what weapon do we choose, so that we
solve one problem and hopefully get the most collateral benefit?

Converting KVs into an interface and subclassing them, as you say, seems as well as a major
overhaul of the code base. Do we really want this right now? And what does it give us besides
the basis for the problem at hand?
                
> 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

        

Mime
View raw message