[
https://issues.apache.org/jira/browse/HBASE-14548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15404473#comment-15404473
]
Hudson commented on HBASE-14548:
--------------------------------
FAILURE: Integrated in HBase-0.98-matrix #379 (See
[https://builds.apache.org/job/HBase-0.98-matrix/379/])
HBASE-14548 Expand how table coprocessor jar and dependency path can be
(apurtell: rev f750acb751c5cc3b4a3292451c0504942b62bf39)
*
hbase-common/src/test/java/org/apache/hadoop/hbase/util/TestCoprocessorClassLoader.java
*
hbase-common/src/main/java/org/apache/hadoop/hbase/util/CoprocessorClassLoader.java
> Expand how table coprocessor jar and dependency path can be specified
> ---------------------------------------------------------------------
>
> Key: HBASE-14548
> URL: https://issues.apache.org/jira/browse/HBASE-14548
> Project: HBase
> Issue Type: Improvement
> Components: Coprocessors
> Affects Versions: 1.2.0
> Reporter: Jerry He
> Assignee: Xiang Li
> Fix For: 2.0.0, 1.4.0, 0.98.21
>
> Attachments: HBASE-14548-1.2.0-v0.patch, HBASE-14548-1.2.0-v1.patch,
> HBASE-14548-1.2.0-v2.patch, HBASE-14548-branch-1-v2.patch,
> HBASE-14548-master-v1.patch, HBASE-14548-master-v2.patch
>
>
> Currently you can specify the location of the coprocessor jar in the table
> coprocessor attribute.
> The problem is that it only allows you to specify one jar that implements the
> coprocessor. You will need to either bundle all the dependencies into this
> jar, or you will need to copy the dependencies into HBase lib dir.
> The first option may not be ideal sometimes. The second choice can be
> troublesome too, particularly when the hbase region sever node and dirs are
> dynamically added/created.
> There are a couple things we can expand here. We can allow the coprocessor
> attribute to specify a directory location, probably on hdfs.
> We may even allow some wildcard in there.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
