[ https://issues.apache.org/jira/browse/HBASE-14548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15361701#comment-15361701 ]
Jerry He commented on HBASE-14548: ---------------------------------- Patch looks good, [~water] Thanks for working on it. bq. + Path pathPattern1 = fs.isDirectory(pathPattern) ? The fs.isDirectory works fine on a wildcard path? The tests are all on local file system. You can enhance them to have the test jars on hdfs. You can enhance ClassLoaderTestHelper.buildJar() to the jar on a working dir on hdfs minicluster. This can be done in a separate JIRA if you like. > 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: li xiang > Fix For: 1.2.0 > > Attachments: HBASE-14548-1.2.0-v0.patch, HBASE-14548-1.2.0-v1.patch, > HBASE-14548-master-v1.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)