hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-13106) Ensure endpoint-only table coprocessors can be dynamically loaded
Date Thu, 26 Feb 2015 00:08:04 GMT

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

Andrew Purtell updated HBASE-13106:
    Status: Open  (was: Patch Available)

Hmm.. Cancelling patch. Let me add a case that adds the CP with online update and then tries
the endpoint invocation.

> Ensure endpoint-only table coprocessors can be dynamically loaded
> -----------------------------------------------------------------
>                 Key: HBASE-13106
>                 URL: https://issues.apache.org/jira/browse/HBASE-13106
>             Project: HBase
>          Issue Type: Test
>            Reporter: Andrew Purtell
>            Assignee: Andrew Purtell
>            Priority: Trivial
>             Fix For: 2.0.0, 1.0.1, 1.1.0, 0.98.11
>         Attachments: HBASE-13106.patch
> I came across the blog post http://www.3pillarglobal.com/insights/hbase-coprocessors
and this interesting bit:
> {quote}
> This means that you can load both Observer and Endpoint Coprocessor statically using
the following Method of HTableDescriptor:
> {noformat}
> addCoprocessor(String className, org.apache.hadoop.fs.Path jarFilePath, int priority,
Map<String,String> kvs) throws IOException
> {noformat}
> In my case, the above method worked fine for Observer Coprocessor *but didn’t work
for Endpoint Coprocessor, causing the table to become unavailable and finally I had to restart
my HBase*. The same Endpoint Coprocessor worked fine when loaded statically. Use the above
method for Endpoint Coprocessor with caution.
> {quote}
> To check this I wrote a test, attached. It passes, all seems ok. Guessing the complaint
was due to user error, probably jar placement/path issues.
> Let's still commit the test.

This message was sent by Atlassian JIRA

View raw message