You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrei Dragomir (Commented) (JIRA)" <ji...@apache.org> on 2011/12/16 09:46:30 UTC

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

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

Andrei Dragomir commented on HBASE-5052:
----------------------------------------

We could work on better cleaning the region name, but I think it is far better to depend on something like the hashed name (HRehionInfo.hashCode()). 
                
> 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
>
> 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