[
https://issues.apache.org/jira/browse/MAPREDUCE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12888445#action_12888445
]
Owen O'Malley commented on MAPREDUCE-1938:
------------------------------------------
Doug,
I agree that the kernel code should be split out from libraries, however, that
work is much more involved. I don't see a problem with putting the user's code
first. It is not a security concern. The user's code is only run as the user.
Furthermore, it doesn't actually stop them from loading system classes. They
can exec a new jvm with a new class path of their own choosing.
Therefore, by putting the user's classes last all that we've done is make it
harder for the user to implement hot fixes in their own jobs. That doesn't seem
like a good goal.
> Ability for having user's classes take precedence over the system classes for
> tasks' classpath
> ----------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-1938
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1938
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: job submission, task, tasktracker
> Reporter: Devaraj Das
> Fix For: 0.22.0
>
> Attachments: mr-1938-bp20.patch
>
>
> It would be nice to have the ability in MapReduce to allow users to specify
> for their jobs alternate implementations of classes that are already defined
> in the MapReduce libraries. For example, an alternate implementation for
> CombineFileInputFormat.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
