hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Virag Kothari (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-12126) Region server coprocessor endpoint
Date Tue, 30 Sep 2014 22:21:33 GMT

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

Virag Kothari updated HBASE-12126:
----------------------------------
    Attachment: HBASE-12126-0.98.patch

Attached is the 0.98 patch for initial review. Work on master is WIP

{code}
 if (CoprocessorService.class.isAssignableFrom(c)) {
          this.regionServerServices.registerService(((CoprocessorService) impl).getService());
          break;
        }
{code}
With the above code in patch, coprocessors like AccessController serving  as region endpoint
and  as an observer for Regionserver  will now also be registered as endpoint for region server

To avoid this, does it make sense to have MasterCoprocessorService, RegionCoprocessorService
and RegionServerCoprocessorService instead of a generic CoprocessorService? (for master branch
)


> Region server coprocessor endpoint
> ----------------------------------
>
>                 Key: HBASE-12126
>                 URL: https://issues.apache.org/jira/browse/HBASE-12126
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Virag Kothari
>         Attachments: HBASE-12126-0.98.patch
>
>
> Primary use case in HBASE-12125 but being able to make endpoint calls against region
server can be useful in general.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message