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 "Doug Cutting (JIRA)" <ji...@apache.org> on 2006/05/19 21:56:31 UTC
[jira] Commented: (HADOOP-232) jar files sent to task tracker
should override existing jar
[ http://issues.apache.org/jira/browse/HADOOP-232?page=comments#action_12412583 ]
Doug Cutting commented on HADOOP-232:
-------------------------------------
This is a security issue. Typically there should not be multiple versions of a resource on the classpath. If there are, what's to be trusted, the one local to the machine, or the one included in the job? We don't want folks to be able to, e.g. include new versions of Hadoop's internal classes in a job. Nor do we wish them to be able to override non-overrideable job settings, which this would permit.
Can you elaborate on the case where you needed this feature?
> jar files sent to task tracker should override existing jar
> -----------------------------------------------------------
>
> Key: HADOOP-232
> URL: http://issues.apache.org/jira/browse/HADOOP-232
> Project: Hadoop
> Type: Bug
> Components: mapred
> Reporter: Yoram Arnon
> Assignee: Milind Bhandarkar
> Priority: Minor
> Attachments: hadoop-232.patch
>
> jar files sent to task tracker are appended to list, rather than prepended to it.
> this results in the original jar getting executed, although a new one was sent - not the intent.
--
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