[
https://issues.apache.org/jira/browse/HBASE-14548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15356266#comment-15356266
]
Hadoop QA commented on HBASE-14548:
-----------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 3s {color}
| {color:red} HBASE-14548 does not apply to master. Rebase required? Wrong
Branch? See https://yetus.apache.org/documentation/0.2.1/precommit-patchnames
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12813609/HBASE-14548-1.2.0-v0.patch
|
| JIRA Issue | HBASE-14548 |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/2431/console |
| Powered by | Apache Yetus 0.2.1 http://yetus.apache.org |
This message was automatically generated.
> 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
>
>
> 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)
