[
https://issues.apache.org/jira/browse/MAPREDUCE-5165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13635378#comment-13635378
]
jay vyas commented on MAPREDUCE-5165:
-------------------------------------
I have just found that rehashes contents from another JIRA
https://issues.apache.org/jira/browse/MAPREDUCE-3169... and there is a
MiniMRYarnCluster in fact in the mapreduce package.
So.. then... Is MiniMRCluster an artifact of the MR1 days that will be less
used once MR2 takes over ?
Is MiniMrYarnCluster a generic version of MiniMRCluster which will one day
obviate the implementation specific MiniMRCluster altogether for the
Hadoop-MapReduce jobs that are implemented in the MR2 YARN framework?
> 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.
> 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 ?
--
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
