hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jerry He (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-14548) Expand how table coprocessor jar and dependency path can be specified
Date Sun, 10 Jul 2016 01:34:10 GMT

     [ https://issues.apache.org/jira/browse/HBASE-14548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jerry He updated HBASE-14548:
-----------------------------
    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.

  was:
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.


> 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: Xiang Li
>             Fix For: 2.0.0, 1.4.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-branch-1-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)

Mime
View raw message