[ 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