You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2015/02/26 01:04:05 UTC

[jira] [Created] (HBASE-13106) Ensure endpoint-only table coprocessors can be dynamically loaded

Andrew Purtell created HBASE-13106:
--------------------------------------

             Summary: 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
            Priority: Trivial
             Fix For: 2.0.0, 1.0.1, 1.1.0, 0.98.11


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