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 (Created) (JIRA)" <ji...@apache.org> on 2011/12/16 09:46:30 UTC
[jira] [Created] (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)
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
[jira] [Updated] (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)
Posted by "Zhihong Yu (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zhihong Yu updated HBASE-5052:
------------------------------
Fix Version/s: 0.94.0
0.92.0
Hadoop Flags: Reviewed
> 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, 0.94.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
[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)
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ 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
[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)
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13183971#comment-13183971 ]
Hudson commented on HBASE-5052:
-------------------------------
Integrated in HBase-TRUNK #2617 (See [https://builds.apache.org/job/HBase-TRUNK/2617/])
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/trunk/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
[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)
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13182182#comment-13182182 ]
Hudson commented on HBASE-5052:
-------------------------------
Integrated in HBase-0.92 #234 (See [https://builds.apache.org/job/HBase-0.92/234/])
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
[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)
Posted by "Zhihong Yu (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13176928#comment-13176928 ]
Zhihong Yu commented on HBASE-5052:
-----------------------------------
+1 on patch.
TestCoprocessorEndpoint itself isn't stable.
> 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, 0.94.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
[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)
Posted by "Andrei Dragomir (Commented) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (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)
Posted by "Andrei Dragomir (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrei Dragomir updated HBASE-5052:
-----------------------------------
Status: Patch Available (was: Open)
> 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
> 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
[jira] [Updated] (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)
Posted by "stack (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-5052:
-------------------------
Resolution: Fixed
Fix Version/s: (was: 0.94.0)
Status: Resolved (was: Patch Available)
Committed branch and trunk. Thanks for the patch Andrei.
> 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
[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)
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13182203#comment-13182203 ]
Hudson commented on HBASE-5052:
-------------------------------
Integrated in HBase-TRUNK-security #67 (See [https://builds.apache.org/job/HBase-TRUNK-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/trunk/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
[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)
Posted by "Hadoop QA (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13176919#comment-13176919 ]
Hadoop QA commented on HBASE-5052:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12507668/HBASE-5052.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.
-1 javadoc. The javadoc tool appears to have generated -151 warning messages.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
-1 findbugs. The patch appears to introduce 76 new Findbugs (version 1.3.9) warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
-1 core tests. The patch failed these unit tests:
org.apache.hadoop.hbase.coprocessor.TestCoprocessorEndpoint
org.apache.hadoop.hbase.mapred.TestTableMapReduce
org.apache.hadoop.hbase.mapreduce.TestHFileOutputFormat
Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/615//testReport/
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/615//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/615//console
This message is automatically generated.
> 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
> 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
[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)
Posted by "Hadoop QA (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13170898#comment-13170898 ]
Hadoop QA commented on HBASE-5052:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12507668/HBASE-5052.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.
-1 javadoc. The javadoc tool appears to have generated -152 warning messages.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
-1 findbugs. The patch appears to introduce 76 new Findbugs (version 1.3.9) warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
-1 core tests. The patch failed these unit tests:
org.apache.hadoop.hbase.coprocessor.TestMasterObserver
org.apache.hadoop.hbase.regionserver.wal.TestLogRolling
org.apache.hadoop.hbase.client.TestInstantSchemaChange
org.apache.hadoop.hbase.master.TestDistributedLogSplitting
Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/519//testReport/
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/519//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/519//console
This message is automatically generated.
> 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
> 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
[jira] [Assigned] (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)
Posted by "Zhihong Yu (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zhihong Yu reassigned HBASE-5052:
---------------------------------
Assignee: Andrei Dragomir
> 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
> 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
[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)
Posted by "Zhihong Yu (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13175275#comment-13175275 ]
Zhihong Yu commented on HBASE-5052:
-----------------------------------
@Andrei:
Have you considered possible collision introduced by the proposed change ?
> 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
> 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
[jira] [Updated] (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)
Posted by "Andrei Dragomir (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrei Dragomir updated HBASE-5052:
-----------------------------------
Attachment: HBASE-5052.patch
> 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
> 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