Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Sun, 8 Jan 2012 08:28:41 +0000 (UTC)
From: "Hudson (Commented) (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <812955746.19825.1326011321046.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <268588491.18747.1324025190718.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HBASE-5052) The path where a dynamically loaded
 coprocessor jar is copied on the local file system depends on the region
 name (and implicitly, the start key)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hudson commented on HBASE-5052:
-------------------------------

Integrated in HBase-0.92-security #67 (See [https://builds.apache.org/job/HBase-0.92-security/67/])
    HBASE-5052 The path where a dynamically loaded coprocessor jar is copied on the local file system depends on the region name (and implicitly, the start key)

stack : 
Files : 
* /hbase/branches/0.92/CHANGES.txt
* /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/regionserver/RegionCoprocessorHost.java

                
> The path where a dynamically loaded coprocessor jar is copied on the local file system depends on the region name (and implicitly, the start key)
> -------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-5052
>                 URL: https://issues.apache.org/jira/browse/HBASE-5052
>             Project: HBase
>          Issue Type: Bug
>          Components: coprocessors
>    Affects Versions: 0.92.0
>            Reporter: Andrei Dragomir
>            Assignee: Andrei Dragomir
>             Fix For: 0.92.0
>
>         Attachments: HBASE-5052.patch
>
>
> When loading a coprocessor from hdfs, the jar file gets copied to a path on the local filesystem, which depends on the region name, and the region start key. The name is "cleaned", but not enough, so when you have filesystem unfriendly characters (/?:, etc), the coprocessor is not loaded, and an error is thrown

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira