[ http://issues.apache.org/jira/browse/HADOOP-189?page=comments#action_12377510 ]
Doug Cutting commented on HADOOP-189: ------------------------------------- > Tracing, I see that any new class will have null for ClassLoader For this patch to work your, e.g., Mapper class needs to only be in the job jar, not also on the classpath built by bin/hadoop. If you are able to instantiate classes in the job jar, and they show up with the bootstrap class loader, then that means the jar file is somehow on the bootstrap classpath, which it should not be after the changes to 'bin/hadoop jar' made in the patch. Is that how you are starting things? Another potential problem could be that the URLClassloader is not correctly constructed. The urls added must be either a jar file or end in slashes. It might be useful to log the urls added to the path in LocalJobRunner to check this. > Add job jar lib, classes, etc. to CLASSPATH when in standalone mode > ------------------------------------------------------------------- > > Key: HADOOP-189 > URL: http://issues.apache.org/jira/browse/HADOOP-189 > Project: Hadoop > Type: New Feature > Components: mapred > Reporter: [EMAIL PROTECTED] > Attachments: local-jar.patch > > Currently, in standalone mode, hadoop is unable to launch other than the > most basic of job jars where 'basic' is a job jar with nought but class files > at top level of the jar with Main-Class pointing at entry point. If the job > jar has dependencies on jars under the job jar lib or there are job jar > plugins in the classes dir, etc., these dependencies are not loaded and the > job fails launch. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
