[
https://issues.apache.org/jira/browse/HADOOP-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507899
]
Runping Qi commented on HADOOP-1521:
------------------------------------
Well, this patch may work (I have not tried yet, but I believe the approach
will work) for this case, but I think it only address this specific case.
Plus, it does not sound right
logically to make ValueAggregatorJob take a representative class name
(think about how do you explain it?). The right solution is that the user
should be able to
specify any jar(s) and Hadoop should ship the jar(s) and put them on the class
path in the
executing environment.
> 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
> Assignee: Enis Soztutar
> Attachments: valueAggregator_v1.0.patch
>
>
> 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.
