hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harsh J (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HADOOP-4416) class names in Configuration are not resolved if the configuration value has a white space
Date Thu, 29 Dec 2011 07:10:31 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-4416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Harsh J resolved HADOOP-4416.
-----------------------------

    Resolution: Not A Problem

We trim in these functions today. This was fixed in more recent jiras. This one is now not
needed.
                
> 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 Common
>          Issue Type: Bug
>         Environment: all
>            Reporter: Alejandro Abdelnur
>            Assignee: Abhijit Bagri
>         Attachments: HADOOP-4416-v2.patch, HADOOP-4416-v3.patch, HADOOP-4416-v4.patch,
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.
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

        

Mime
View raw message