[HBASE-14548] Expand how table coprocessor jar and dependency path can be specified

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2.0
• Fix Version/s: 1.4.0, 0.98.21, 2.0.0
• Component/s: Coprocessors
• Hadoop Flags: Reviewed

Release Note

Allow a directory containing the jars or some wildcards to be specified, such as: hdfs://namenode:port/user/hadoop-user/
or
hdfs://namenode:port/user/hadoop-user/*.jar

Please note that if a directory is specified, all jar files(.jar) directly in the directory are added, but it does not search files in the subtree rooted in the directory.
Do not contain any wildcard if you would like to specify a directory.

• Assignee: Xiang Li
• Reporter: Jerry He
• Created: 03/Oct/15 00:07
• Updated: 24/Jun/22 19:25
• Resolved: 10/Jul/16 01:28

Description

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.

Issue Links

• is related to: HBASE-13907 Document how to deploy a coprocessor