[
https://issues.apache.org/jira/browse/HBASE-14548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363259#comment-15363259
]
Jerry He commented on HBASE-14548:
----------------------------------
Ok, Wildcard path is probably caught by FileSytem.isDirectory() as the
FileNotFoundException and return false.
I think we only need to guarantee these basic cases work:
1. No regression. If user specifies a jar path, it should work as it currently
is.
2. If it is a directory path, it should work by including its jars.
3. Support jar path wildcard at the end level of the path string.
The patch looks good. See if [~apurtell] [~anoop.hbase] have comments.
> 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: 2.0.0
>
> Attachments: HBASE-14548-1.2.0-v0.patch, HBASE-14548-1.2.0-v1.patch,
> HBASE-14548-1.2.0-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)
