hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Clay B. (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-16700) Allow for coprocessor whitelisting
Date Thu, 10 Nov 2016 00:40:59 GMT

     [ https://issues.apache.org/jira/browse/HBASE-16700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Clay B. updated HBASE-16700:
    Attachment: HBASE-16700.001.patch

Thanks Ted! Including InterfaceAudience; moving the configuration getter out of the for loop;
adding a test classification; correcting the LogFactory class; removing trailing white space.
Two things I noticed: correcting to use a String() instead of Path() for the success log message
and removing extraneous log message "Checking coprocessor %s".

> 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.
>            Priority: Minor
>              Labels: security
>         Attachments: HBASE-16700.000.patch, HBASE-16700.001.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