You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Clay B. (JIRA)" <ji...@apache.org> on 2016/11/09 22:37:58 UTC

[jira] [Updated] (HBASE-16700) Allow for coprocessor whitelisting

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

Clay B. updated HBASE-16700:
----------------------------
          Labels: security  (was: )
    Release Note: Provides ability to restrict table coprocessors based on HDFS path whitelist. (Particularly useful for allowing Phoenix coprocessors but not arbitrary user created coprocessors.)
          Status: Patch Available  (was: Open)

> 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
>
> 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
(v6.3.4#6332)