[
https://issues.apache.org/jira/browse/HADOOP-4416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12642420#action_12642420
]
abagri edited comment on HADOOP-4416 at 10/24/08 2:05 AM:
-----------------------------------------------------------------
As per discussion on HADOOP-4212, I think a compatible changes list should
apply for the following functions. Individual function trims will be needed
getInt()
getLong()
getFloat()
getBoolean()
getRange()
getClasses()
getClass()
I am not sure about getString() and getStringCollection(), Comments?
was (Author: abagri):
As per discussion on HADOOP-4212, I think a compatible changes list should
apply for the following functions. Individual function trims will be needed
getInt()
getLong()
getHexDigits()
getFloat()
getBoolean()
getRange()
getClasses()
getClass()
I am not sure about getString() and getStringCollection(), Comments?
> 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
> Assignee: Abhijit Bagri
> Attachments: HADOOP-4416.patch
>
>
> 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.
