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 "Enis Soztutar (JIRA)" <ji...@apache.org> on 2007/07/09 14:52:05 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_12511104 ]
Enis Soztutar commented on HADOOP-1521:
---------------------------------------
Currently we ship only one job file with the application, and this job file is searched by the help of a class in the job file. Unless we do decide to take the above approach(which i personally don't like), i think it is the aggragetor's responsibility to obtain the client class(or jar file). In able to proceed I suggest we fire a new issue, apply the patch there, and resolve this issue as wont fix. Any thoughts ?
> 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.