hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Abdelnur (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-3169) Create a new MiniMRCluster equivalent which only provides client APIs cross MR1 and MR2
Date Fri, 28 Oct 2011 21:48:33 GMT

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

Alejandro Abdelnur commented on MAPREDUCE-3169:
-----------------------------------------------

I'm suggesting that MiniMRCluster becomes a wrapper of MiniMRClientCluster. The constructors
would be kept not break old tests, only propagating configs that make sense to MiniMRClientCluster.


In addition MiniMRCluster API should be either trimmed of MR1 specific methods or make them
throw UnsupportedOperationException. 

While this would break some tests, most likely will be MR1 tests only. And, if it is the case
for other projects, then those projects will have to make some changes to accomodate MR2.
(although I'd believe this would be minimal or NIL).

                
> Create a new MiniMRCluster equivalent which only provides client APIs cross MR1 and MR2
> ---------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-3169
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3169
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: mrv1, mrv2, test
>    Affects Versions: 0.23.0
>            Reporter: Todd Lipcon
>            Assignee: Ahmed Radwan
>         Attachments: MAPREDUCE-3169-0.20-security.patch, MAPREDUCE-3169-truck.patch
>
>
> Many dependent projects like HBase, Hive, Pig, etc, depend on MiniMRCluster for writing
tests. Many users do as well. MiniMRCluster, however, exposes MR implementation details like
the existence of TaskTrackers, JobTrackers, etc, since it was used by MR1 for testing the
server implementations as well.
> This JIRA is to create a new interface which could be implemented either by MR1 or MR2
that exposes only the client-side portions of the MR framework. Ideally it would be "recompile-compatible"
with MiniMRCluster for most applications, and the MR1 implementation could be backported to
20x branch. Thus, dependent projects like HBase could migrate to this implementation and test
against both MR1 and MR2. We can also use this to port over the current functional tests that
use only the client-side features of MiniMRCluster.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message