You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2017/07/01 05:54:03 UTC

[jira] [Commented] (HBASE-13866) Add endpoint coprocessor to the section hbase.coprocessor.region.classes in HBase book

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

Hudson commented on HBASE-13866:
--------------------------------

SUCCESS: Integrated in Jenkins build HBase-Trunk_matrix #3291 (See [https://builds.apache.org/job/HBase-Trunk_matrix/3291/])
HBASE-13866 Clarify description of hbase.coprocessor.region.classes (stack: rev 92f74d6f1ed23c7525742f9c81a44594b8d8b8e6)
* (edit) hbase-common/src/main/resources/hbase-default.xml


> Add endpoint coprocessor to the section hbase.coprocessor.region.classes in HBase book
> --------------------------------------------------------------------------------------
>
>                 Key: HBASE-13866
>                 URL: https://issues.apache.org/jira/browse/HBASE-13866
>             Project: HBase
>          Issue Type: Bug
>          Components: documentation
>    Affects Versions: 2.0.0
>            Reporter: Vladimir Rodionov
>            Assignee: Misty Stanley-Jones
>            Priority: Trivial
>             Fix For: 2.0.0
>
>         Attachments: HBASE-13866.patch
>
>
> {quote}
> hbase.coprocessor.region.classes
>     Description
>     A comma-separated list of Coprocessors that are loaded by default on all tables. For any override coprocessor method, these classes will be called in order. After implementing your own Coprocessor, just put it in HBase’s classpath and add the fully qualified class name here. A coprocessor can also be loaded on demand by setting HTableDescriptor.
> {quote}
> This must be more specific: not Coprocessors, but Region observers and *endpoint coprocessors*.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)