Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7DC3F107A0 for ; Tue, 23 Apr 2013 19:23:16 +0000 (UTC) Received: (qmail 24171 invoked by uid 500); 23 Apr 2013 19:23:16 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 24133 invoked by uid 500); 23 Apr 2013 19:23:16 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 24008 invoked by uid 99); 23 Apr 2013 19:23:16 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Apr 2013 19:23:16 +0000 Date: Tue, 23 Apr 2013 19:23:16 +0000 (UTC) From: "Andrew Purtell (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-8400) Load coprocessor jar from various protocols (HTTP, HTTPS, FTP, etc.) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-8400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13639445#comment-13639445 ] Andrew Purtell commented on HBASE-8400: --------------------------------------- I believe what you are asking for is an alternative classloader that fetches JARs from some other type of storage. I think we can make which classloader to use for coprocessors configurable. We are consolidating classloaders in HBASE-8327. You should start there. > Load coprocessor jar from various protocols (HTTP, HTTPS, FTP, etc.) > -------------------------------------------------------------------- > > Key: HBASE-8400 > URL: https://issues.apache.org/jira/browse/HBASE-8400 > Project: HBase > Issue Type: Improvement > Components: Coprocessors > Affects Versions: 0.94.3, 0.98.0 > Reporter: Julian Zhou > Assignee: Julian Zhou > Priority: Minor > Fix For: 0.94.3, 0.98.0 > > > In some application testing and production environment, after developed coprocessors and generated jars, currently we need to transfer them to hdfs first, then specify the URI in table descriptor to point to HDFS compatible addresses of jars. Common used HTTP/HTTPS/FTP or other protocols were not supported yet? To save time and make the life easier without transferring from http/ftp or other servers, just modified the CoprocessorHost to use http/ftp url connection (http and ftp servers are the most cases need to be support) to stream jars to coprocessor jar spaces automatically. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira