Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Sat, 3 Oct 2015 00:07:26 +0000 (UTC)
From: "Jerry He (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12902231.1443830826000.15421.1443830846500@Atlassian.JIRA>
In-Reply-To: <JIRA.12902231.1443830826000@Atlassian.JIRA>
References: <JIRA.12902231.1443830826000@Atlassian.JIRA>
 <JIRA.12902231.1443830826848@arcas>
Subject: [jira] [Created] (HBASE-14548) Expand how table coprocessor jar and
 dependency path can be specified
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Jerry He created HBASE-14548:
--------------------------------

             Summary: 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
            Reporter: Jerry He


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)