You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Owen O'Malley (JIRA)" <ji...@apache.org> on 2007/06/23 08:49:26 UTC
[jira] Commented: (HADOOP-1521) Hadoop mapreduce should always
ship the jar file(s) specified by the user
[ https://issues.apache.org/jira/browse/HADOOP-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507566 ]
Owen O'Malley commented on HADOOP-1521:
---------------------------------------
I don't understand what went wrong. Did the jar not exist? Was the representative class found in another jar? Applications can explicitly specify a jar file and that jar file WILL be used. Most applications use the method that sets the jar file based on a representative class. That can fail if the representative class is both in the "hadoop system" jars and the user's jar file.
> Hadoop mapreduce should always ship the jar file(s) specified by the user
> --------------------------------------------------------------------------
>
> Key: HADOOP-1521
> URL: https://issues.apache.org/jira/browse/HADOOP-1521
> Project: Hadoop
> Issue Type: Bug
> Components: mapred
> Reporter: Runping Qi
>
> when I run a hadoop job like:
> bin/hadoop jar myjar org.apache.hadoop.mapred.lib.aggregate.ValueAggregatorJob other_args
> myjar is not shipped. The job failed because the class loader cannot find the classes specified in myjar.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.