[
https://issues.apache.org/jira/browse/HADOOP-4416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639817#action_12639817
]
Alejandro Abdelnur commented on HADOOP-4416:
--------------------------------------------
This is not really an instance of HADOOP-4212. Personally I would agree that
for configuration values you can safely trim them, but I can see people
opposing to it.
For class names it is different, you don't want the spaces.
And it should be done in the {{getClassByName()}} method to properly handle the
{{getClasses()}} method, this is important for values like:
{code}
<property>
<name>io.compression.codecs</name>
<value>org.apache.hadoop.io.compress.DefaultCodec,org.apache.hadoop.io.compress.GzipCodec,org.apache.hadoop.io.compress.BZip2Codec</value>
</property>
{code}
Where if you have several classes you may want to have an enter between commas
for readability.
> class names in Configuration are not resolved if the configuration value has
> a white space
> -------------------------------------------------------------------------------------------
>
> Key: HADOOP-4416
> URL: https://issues.apache.org/jira/browse/HADOOP-4416
> Project: Hadoop Core
> Issue Type: Bug
> Environment: all
> Reporter: Alejandro Abdelnur
> Fix For: 0.19.0
>
>
> If an entry in the configuration used for a class contains spaces or enters
> before or after the {{getClass}} and {{getClasses}} methods fail to resolve
> the class.
> For example:
> {code}
> <property>
> <name>mapred.mapper.class</name>
> <value>
> com.foo.MyMapper
> </value>
> </property>
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
