You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-dev@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2014/07/24 02:02:43 UTC

[jira] [Resolved] (MAPREDUCE-1001) Reducing code duplication in Mumak

     [ https://issues.apache.org/jira/browse/MAPREDUCE-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Allen Wittenauer resolved MAPREDUCE-1001.
-----------------------------------------

    Resolution: Won't Fix

Mumak has been removed from Hadoop.

> Reducing code duplication in Mumak
> ----------------------------------
>
>                 Key: MAPREDUCE-1001
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1001
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Hong Tang
>
> The first release of Mumak (MAPREDUCE-728) introduces some coupling between the core mapred code with Mumak code. Specifically, New constructors are added to JobTracker and JobInProgress to allow simulator to subclass and alter JT/JIP behavior. This could be a code maintenance overhead when new changes have to be ported to either the added constructors or the simulation subclasses.
> It would be nice to refactor the constructors of JobTracker and JobInProgress to avoid as much code duplication as possible.



--
This message was sent by Atlassian JIRA
(v6.2#6252)