hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "li xiang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14548) Expand how table coprocessor jar and dependency path can be specified
Date Wed, 06 Jul 2016 07:08:11 GMT

    [ https://issues.apache.org/jira/browse/HBASE-14548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363889#comment-15363889

li xiang commented on HBASE-14548:

Hi Jerry, there is a format problem in my comment yesterday which I did not noticed.
It should be corrected as :
1. I tested FileSytem.isDirectory() by a separate program, against the path with wildcard.
It works as expected for the following inputs, for example, "/user/hbase/\*.jar" or "/user/hbase/coprocessor.\*",
isDirectory() returns false.
I forgot to add the escape character "\" in front of two "*" in the sentence above, so the
system displays the words between those two "*" into bold.

Sorry if it made you confused. 

> 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
> 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

View raw message