hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16700) Allow for coprocessor whitelisting
Date Thu, 15 Dec 2016 22:26:58 GMT

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

stack commented on HBASE-16700:

[~clayb] Thanks for patch. Suggest add a release note since this a nice new feature. Just
write something that would work for an operator audience. I think you know this perspective

I see the added test can fail: https://builds.apache.org/view/All/job/HBase-Trunk_matrix/jdk=JDK%201.8%20(latest),label=Hadoop/2135/testReport/junit/org.apache.hadoop.hbase.security.access/TestCoprocessorWhitelistMasterObserver/org_apache_hadoop_hbase_security_access_TestCoprocessorWhitelistMasterObserver/

It failed also on a hadoopqa build. What you think? Should it be a large test so it has more
time to run or  did something go wrong in this run.


> Allow for coprocessor whitelisting
> ----------------------------------
>                 Key: HBASE-16700
>                 URL: https://issues.apache.org/jira/browse/HBASE-16700
>             Project: HBase
>          Issue Type: Improvement
>          Components: Coprocessors
>            Reporter: Clay B.
>            Assignee: Clay B.
>            Priority: Minor
>              Labels: security
>             Fix For: 2.0.0
>         Attachments: HBASE-16700.000.patch, HBASE-16700.001.patch, HBASE-16700.002.patch,
HBASE-16700.003.patch, HBASE-16700.004.patch, HBASE-16700.005.patch, HBASE-16700.006.patch,
HBASE-16700.007.patch, HBASE-16700.008.patch
> Today one can turn off all non-system coprocessors with {{hbase.coprocessor.user.enabled}}
however, this disables very useful things like Apache Phoenix's coprocessors. Some tenants
of a multi-user HBase may also need to run bespoke coprocessors. But as an operator I would
not want wanton coprocessor usage. Ideally, one could do one of two things:
> * Allow coprocessors defined in {{hbase-site.xml}} -- this can only be administratively
changed in most cases
> * Allow coprocessors from table descriptors but only if the coprocessor is whitelisted

This message was sent by Atlassian JIRA

View raw message