You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Matteo Bertozzi (JIRA)" <ji...@apache.org> on 2012/04/27 23:56:50 UTC
[jira] [Created] (HBASE-5893) Allow spaces in coprocessor conf (aka
trim() className)
Matteo Bertozzi created HBASE-5893:
--------------------------------------
Summary: Allow spaces in coprocessor conf (aka trim() className)
Key: HBASE-5893
URL: https://issues.apache.org/jira/browse/HBASE-5893
Project: HBase
Issue Type: Bug
Components: coprocessors
Affects Versions: 0.92.1, 0.94.0, 0.96.0
Reporter: Matteo Bertozzi
Assignee: Matteo Bertozzi
Priority: Minor
This is annoying especially for coprocessors where you've long class name.
but maybe is a bug of Configuration.getStrings() that doesn't trim each string.
When you've comma separated values like in the coprocessors case, you've to pack together your values without spaces ("v1,v2,v3,...") otherwise the coprocessor is not loaded because the class name with spaces is not found.
{code}
<property>
<name>hbase.coprocessor.master.classes</name>
<value>
org.apache.hadoop.hbase.security.token.TokenProvider,
org.apache.hadoop.hbase.security.access.AccessController
</value>
</property>
{code}
--
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-5893) Allow spaces in coprocessor conf
(aka trim() className)
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13264243#comment-13264243 ]
Hudson commented on HBASE-5893:
-------------------------------
Integrated in HBase-0.92 #392 (See [https://builds.apache.org/job/HBase-0.92/392/])
HBASE-5893 Allow spaces in coprocessor conf (aka trim() className) (Revision 1331641)
Result = SUCCESS
stack :
Files :
* /hbase/branches/0.92/CHANGES.txt
* /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/coprocessor/CoprocessorHost.java
> Allow spaces in coprocessor conf (aka trim() className)
> -------------------------------------------------------
>
> Key: HBASE-5893
> URL: https://issues.apache.org/jira/browse/HBASE-5893
> Project: HBase
> Issue Type: Bug
> Components: coprocessors
> Affects Versions: 0.92.1, 0.94.0, 0.96.0
> Reporter: Matteo Bertozzi
> Assignee: Matteo Bertozzi
> Priority: Minor
> Labels: conf, coprocessors
> Fix For: 0.92.2, 0.94.0
>
> Attachments: HBASE-5893-v0.patch
>
>
> This is annoying especially for coprocessors where you've long class name.
> but maybe is a bug of Configuration.getStrings() that doesn't trim each string.
> When you've comma separated values like in the coprocessors case, you've to pack together your values without spaces ("v1,v2,v3,...") otherwise the coprocessor is not loaded because the class name with spaces is not found.
> {code}
> <property>
> <name>hbase.coprocessor.master.classes</name>
> <value>
> org.apache.hadoop.hbase.security.token.TokenProvider,
> org.apache.hadoop.hbase.security.access.AccessController
> </value>
> </property>
> {code}
--
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-5893) Allow spaces in coprocessor conf
(aka trim() className)
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13268872#comment-13268872 ]
Hudson commented on HBASE-5893:
-------------------------------
Integrated in HBase-0.92-security #106 (See [https://builds.apache.org/job/HBase-0.92-security/106/])
HBASE-5893 Allow spaces in coprocessor conf (aka trim() className) (Revision 1331641)
Result = SUCCESS
stack :
Files :
* /hbase/branches/0.92/CHANGES.txt
* /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/coprocessor/CoprocessorHost.java
> Allow spaces in coprocessor conf (aka trim() className)
> -------------------------------------------------------
>
> Key: HBASE-5893
> URL: https://issues.apache.org/jira/browse/HBASE-5893
> Project: HBase
> Issue Type: Bug
> Components: coprocessors
> Affects Versions: 0.92.1, 0.94.0, 0.96.0
> Reporter: Matteo Bertozzi
> Assignee: Matteo Bertozzi
> Priority: Minor
> Labels: conf, coprocessors
> Fix For: 0.92.2, 0.94.0
>
> Attachments: HBASE-5893-v0.patch
>
>
> This is annoying especially for coprocessors where you've long class name.
> but maybe is a bug of Configuration.getStrings() that doesn't trim each string.
> When you've comma separated values like in the coprocessors case, you've to pack together your values without spaces ("v1,v2,v3,...") otherwise the coprocessor is not loaded because the class name with spaces is not found.
> {code}
> <property>
> <name>hbase.coprocessor.master.classes</name>
> <value>
> org.apache.hadoop.hbase.security.token.TokenProvider,
> org.apache.hadoop.hbase.security.access.AccessController
> </value>
> </property>
> {code}
--
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-5893) Allow spaces in coprocessor conf (aka
trim() className)
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-5893:
-------------------------
Resolution: Fixed
Fix Version/s: 0.94.0
0.92.2
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Committed to 0.92, 0.94, and trunk (Usability). Thanks for the patch Matteo.
> Allow spaces in coprocessor conf (aka trim() className)
> -------------------------------------------------------
>
> Key: HBASE-5893
> URL: https://issues.apache.org/jira/browse/HBASE-5893
> Project: HBase
> Issue Type: Bug
> Components: coprocessors
> Affects Versions: 0.92.1, 0.94.0, 0.96.0
> Reporter: Matteo Bertozzi
> Assignee: Matteo Bertozzi
> Priority: Minor
> Labels: conf, coprocessors
> Fix For: 0.92.2, 0.94.0
>
> Attachments: HBASE-5893-v0.patch
>
>
> This is annoying especially for coprocessors where you've long class name.
> but maybe is a bug of Configuration.getStrings() that doesn't trim each string.
> When you've comma separated values like in the coprocessors case, you've to pack together your values without spaces ("v1,v2,v3,...") otherwise the coprocessor is not loaded because the class name with spaces is not found.
> {code}
> <property>
> <name>hbase.coprocessor.master.classes</name>
> <value>
> org.apache.hadoop.hbase.security.token.TokenProvider,
> org.apache.hadoop.hbase.security.access.AccessController
> </value>
> </property>
> {code}
--
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-5893) Allow spaces in coprocessor conf
(aka trim() className)
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13264058#comment-13264058 ]
Hadoop QA commented on HBASE-5893:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12524934/HBASE-5893-v0.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 hadoop23. The patch compiles against the hadoop 0.23.x profile.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
-1 findbugs. The patch appears to introduce 2 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 passed unit tests in .
Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/1674//testReport/
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/1674//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/1674//console
This message is automatically generated.
> Allow spaces in coprocessor conf (aka trim() className)
> -------------------------------------------------------
>
> Key: HBASE-5893
> URL: https://issues.apache.org/jira/browse/HBASE-5893
> Project: HBase
> Issue Type: Bug
> Components: coprocessors
> Affects Versions: 0.92.1, 0.94.0, 0.96.0
> Reporter: Matteo Bertozzi
> Assignee: Matteo Bertozzi
> Priority: Minor
> Labels: conf, coprocessors
> Attachments: HBASE-5893-v0.patch
>
>
> This is annoying especially for coprocessors where you've long class name.
> but maybe is a bug of Configuration.getStrings() that doesn't trim each string.
> When you've comma separated values like in the coprocessors case, you've to pack together your values without spaces ("v1,v2,v3,...") otherwise the coprocessor is not loaded because the class name with spaces is not found.
> {code}
> <property>
> <name>hbase.coprocessor.master.classes</name>
> <value>
> org.apache.hadoop.hbase.security.token.TokenProvider,
> org.apache.hadoop.hbase.security.access.AccessController
> </value>
> </property>
> {code}
--
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-5893) Allow spaces in coprocessor conf
(aka trim() className)
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13264422#comment-13264422 ]
Hudson commented on HBASE-5893:
-------------------------------
Integrated in HBase-0.94-security #24 (See [https://builds.apache.org/job/HBase-0.94-security/24/])
HBASE-5893 Allow spaces in coprocessor conf (aka trim() className) (Revision 1331639)
Result = FAILURE
stack :
Files :
* /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/coprocessor/CoprocessorHost.java
> Allow spaces in coprocessor conf (aka trim() className)
> -------------------------------------------------------
>
> Key: HBASE-5893
> URL: https://issues.apache.org/jira/browse/HBASE-5893
> Project: HBase
> Issue Type: Bug
> Components: coprocessors
> Affects Versions: 0.92.1, 0.94.0, 0.96.0
> Reporter: Matteo Bertozzi
> Assignee: Matteo Bertozzi
> Priority: Minor
> Labels: conf, coprocessors
> Fix For: 0.92.2, 0.94.0
>
> Attachments: HBASE-5893-v0.patch
>
>
> This is annoying especially for coprocessors where you've long class name.
> but maybe is a bug of Configuration.getStrings() that doesn't trim each string.
> When you've comma separated values like in the coprocessors case, you've to pack together your values without spaces ("v1,v2,v3,...") otherwise the coprocessor is not loaded because the class name with spaces is not found.
> {code}
> <property>
> <name>hbase.coprocessor.master.classes</name>
> <value>
> org.apache.hadoop.hbase.security.token.TokenProvider,
> org.apache.hadoop.hbase.security.access.AccessController
> </value>
> </property>
> {code}
--
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-5893) Allow spaces in coprocessor conf
(aka trim() className)
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13264241#comment-13264241 ]
Hudson commented on HBASE-5893:
-------------------------------
Integrated in HBase-TRUNK-security #187 (See [https://builds.apache.org/job/HBase-TRUNK-security/187/])
HBASE-5893 Allow spaces in coprocessor conf (aka trim() className) (Revision 1331638)
Result = SUCCESS
stack :
Files :
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/coprocessor/CoprocessorHost.java
> Allow spaces in coprocessor conf (aka trim() className)
> -------------------------------------------------------
>
> Key: HBASE-5893
> URL: https://issues.apache.org/jira/browse/HBASE-5893
> Project: HBase
> Issue Type: Bug
> Components: coprocessors
> Affects Versions: 0.92.1, 0.94.0, 0.96.0
> Reporter: Matteo Bertozzi
> Assignee: Matteo Bertozzi
> Priority: Minor
> Labels: conf, coprocessors
> Fix For: 0.92.2, 0.94.0
>
> Attachments: HBASE-5893-v0.patch
>
>
> This is annoying especially for coprocessors where you've long class name.
> but maybe is a bug of Configuration.getStrings() that doesn't trim each string.
> When you've comma separated values like in the coprocessors case, you've to pack together your values without spaces ("v1,v2,v3,...") otherwise the coprocessor is not loaded because the class name with spaces is not found.
> {code}
> <property>
> <name>hbase.coprocessor.master.classes</name>
> <value>
> org.apache.hadoop.hbase.security.token.TokenProvider,
> org.apache.hadoop.hbase.security.access.AccessController
> </value>
> </property>
> {code}
--
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-5893) Allow spaces in coprocessor conf
(aka trim() className)
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13264230#comment-13264230 ]
Hudson commented on HBASE-5893:
-------------------------------
Integrated in HBase-TRUNK #2823 (See [https://builds.apache.org/job/HBase-TRUNK/2823/])
HBASE-5893 Allow spaces in coprocessor conf (aka trim() className) (Revision 1331638)
Result = FAILURE
stack :
Files :
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/coprocessor/CoprocessorHost.java
> Allow spaces in coprocessor conf (aka trim() className)
> -------------------------------------------------------
>
> Key: HBASE-5893
> URL: https://issues.apache.org/jira/browse/HBASE-5893
> Project: HBase
> Issue Type: Bug
> Components: coprocessors
> Affects Versions: 0.92.1, 0.94.0, 0.96.0
> Reporter: Matteo Bertozzi
> Assignee: Matteo Bertozzi
> Priority: Minor
> Labels: conf, coprocessors
> Fix For: 0.92.2, 0.94.0
>
> Attachments: HBASE-5893-v0.patch
>
>
> This is annoying especially for coprocessors where you've long class name.
> but maybe is a bug of Configuration.getStrings() that doesn't trim each string.
> When you've comma separated values like in the coprocessors case, you've to pack together your values without spaces ("v1,v2,v3,...") otherwise the coprocessor is not loaded because the class name with spaces is not found.
> {code}
> <property>
> <name>hbase.coprocessor.master.classes</name>
> <value>
> org.apache.hadoop.hbase.security.token.TokenProvider,
> org.apache.hadoop.hbase.security.access.AccessController
> </value>
> </property>
> {code}
--
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-5893) Allow spaces in coprocessor conf
(aka trim() className)
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13264227#comment-13264227 ]
Hudson commented on HBASE-5893:
-------------------------------
Integrated in HBase-0.94 #153 (See [https://builds.apache.org/job/HBase-0.94/153/])
HBASE-5893 Allow spaces in coprocessor conf (aka trim() className) (Revision 1331639)
Result = FAILURE
stack :
Files :
* /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/coprocessor/CoprocessorHost.java
> Allow spaces in coprocessor conf (aka trim() className)
> -------------------------------------------------------
>
> Key: HBASE-5893
> URL: https://issues.apache.org/jira/browse/HBASE-5893
> Project: HBase
> Issue Type: Bug
> Components: coprocessors
> Affects Versions: 0.92.1, 0.94.0, 0.96.0
> Reporter: Matteo Bertozzi
> Assignee: Matteo Bertozzi
> Priority: Minor
> Labels: conf, coprocessors
> Fix For: 0.92.2, 0.94.0
>
> Attachments: HBASE-5893-v0.patch
>
>
> This is annoying especially for coprocessors where you've long class name.
> but maybe is a bug of Configuration.getStrings() that doesn't trim each string.
> When you've comma separated values like in the coprocessors case, you've to pack together your values without spaces ("v1,v2,v3,...") otherwise the coprocessor is not loaded because the class name with spaces is not found.
> {code}
> <property>
> <name>hbase.coprocessor.master.classes</name>
> <value>
> org.apache.hadoop.hbase.security.token.TokenProvider,
> org.apache.hadoop.hbase.security.access.AccessController
> </value>
> </property>
> {code}
--
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-5893) Allow spaces in coprocessor conf (aka
trim() className)
Posted by "Matteo Bertozzi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matteo Bertozzi updated HBASE-5893:
-----------------------------------
Attachment: HBASE-5893-v0.patch
> Allow spaces in coprocessor conf (aka trim() className)
> -------------------------------------------------------
>
> Key: HBASE-5893
> URL: https://issues.apache.org/jira/browse/HBASE-5893
> Project: HBase
> Issue Type: Bug
> Components: coprocessors
> Affects Versions: 0.92.1, 0.94.0, 0.96.0
> Reporter: Matteo Bertozzi
> Assignee: Matteo Bertozzi
> Priority: Minor
> Labels: conf, coprocessors
> Attachments: HBASE-5893-v0.patch
>
>
> This is annoying especially for coprocessors where you've long class name.
> but maybe is a bug of Configuration.getStrings() that doesn't trim each string.
> When you've comma separated values like in the coprocessors case, you've to pack together your values without spaces ("v1,v2,v3,...") otherwise the coprocessor is not loaded because the class name with spaces is not found.
> {code}
> <property>
> <name>hbase.coprocessor.master.classes</name>
> <value>
> org.apache.hadoop.hbase.security.token.TokenProvider,
> org.apache.hadoop.hbase.security.access.AccessController
> </value>
> </property>
> {code}
--
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-5893) Allow spaces in coprocessor conf (aka
trim() className)
Posted by "Matteo Bertozzi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matteo Bertozzi updated HBASE-5893:
-----------------------------------
Status: Patch Available (was: Open)
> Allow spaces in coprocessor conf (aka trim() className)
> -------------------------------------------------------
>
> Key: HBASE-5893
> URL: https://issues.apache.org/jira/browse/HBASE-5893
> Project: HBase
> Issue Type: Bug
> Components: coprocessors
> Affects Versions: 0.92.1, 0.94.0, 0.96.0
> Reporter: Matteo Bertozzi
> Assignee: Matteo Bertozzi
> Priority: Minor
> Labels: conf, coprocessors
> Attachments: HBASE-5893-v0.patch
>
>
> This is annoying especially for coprocessors where you've long class name.
> but maybe is a bug of Configuration.getStrings() that doesn't trim each string.
> When you've comma separated values like in the coprocessors case, you've to pack together your values without spaces ("v1,v2,v3,...") otherwise the coprocessor is not loaded because the class name with spaces is not found.
> {code}
> <property>
> <name>hbase.coprocessor.master.classes</name>
> <value>
> org.apache.hadoop.hbase.security.token.TokenProvider,
> org.apache.hadoop.hbase.security.access.AccessController
> </value>
> </property>
> {code}
--
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