hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Abdelnur (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-5165) Create MiniMRCluster version which uses the mapreduce package.
Date Thu, 18 Apr 2013 17:52:13 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-5165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13635418#comment-13635418
] 

Alejandro Abdelnur commented on MAPREDUCE-5165:
-----------------------------------------------

MiniMRCluster has been added to Hadoop2 to enabled backward compatibility for downstream projects
that used Hadoop1 MiniMRCluster in their testcases. In other words, to support legacy stuff.

If you are starting something from scratch you should use the new MiniMRYarnCluster directly.

IMO, I'd close this JIRA as not-a-problem.
                
> Create MiniMRCluster version which uses the mapreduce package.
> --------------------------------------------------------------
>
>                 Key: MAPREDUCE-5165
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5165
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: jay vyas
>            Priority: Minor
>
> The MiniMapRedCluster class references some older mapred.* classes (as per comments below
however, there is the MiniMRYarnCluster, which may aim to replace it). 
> It could be recreated in the mapreduce package to use the Configuration class instead
of JobConf, which would make it simpler to use and integrate with new FS implementations and
test harnesses that use new Configuration (not JobConf) objects to drive tests.
> This could be done many ways:
> 1) using inheritance or else 
> 2) by copying the code directly
> The appropriate implementation depends on wether or not 
> 1) Is it okay for mapreduce.* classes to depend on mapred.* classes ?
> 2) Is the mapred MiniMRCluster implementation going to be deprecated or eliminated anytime?

> 3) What is the future of the JobConf class - which has been deprecated and then undeprecated
?
> Note that This is all intimately linked to the role that MiniMRYarnCluster will play.
 Relevant classes:
> .//hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapred/MiniMRClientCluster.java
> .//hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapred/MiniMRClientClusterFactory.java
> .//hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapred/MiniMRCluster.java
> .//hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapred/MiniMRYarnClusterAdapter.java
> .//hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapreduce/v2/MiniMRYarnCluster.java

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message