Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Mon, 1 Apr 2013 17:55:17 +0000 (UTC)
From: "Alejandro Abdelnur (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: <JIRA.12639466.1364420031073.86214.1364838917570@arcas>
In-Reply-To: <JIRA.12639466.1364420031073@arcas>
References: <JIRA.12639466.1364420031073@arcas>
Subject: [jira] [Commented] (MAPREDUCE-5108) Review support for Binary
 Compatibility for MR applications via YARN
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Alejandro Abdelnur commented on MAPREDUCE-5108:
-----------------------------------------------

Tom is correct, counters API does not work. Oozie uses exclusively the mapred API for job submission/monitoring and counters are an issue. Because of that we need to compile Oozie for Hadoop 1 or Hadoop 2 depending on the target cluster.
                
> Review support for Binary Compatibility for MR applications via YARN
> --------------------------------------------------------------------
>
>                 Key: MAPREDUCE-5108
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5108
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>    Affects Versions: 2.0.3-alpha
>            Reporter: Arun C Murthy
>            Assignee: Zhijie Shen
>            Priority: Blocker
>             Fix For: 2.0.5-beta
>
>
> As we get ready to ship out a beta/stable version of hadoop-2, it makes sense to spend time reviewing support for existing MR applications (hadoop-1) to migrate seamlessly.
> We've done various pieces of work over time, let's track progress and document things clearly. [~zjshen] has done a bunch of testing and results look very promising so far.
> The aim is to support applications using org.apache.hadoop.mapred.* api in a binary compatible manner in hadoop-2 - thus, users can just take existing MR applications jars, point them at YARN clusters and things just work.
> Clearly, we might have some corner cases (haven't seen many so far), including semantics (not just apis); however the intent is to, at least, document them throughly if not actually fix them as feasible.
> Also, it's clear that we will *not* be able to support org.apache.hadoop.mapreduce api in a *binary compatible* manner due to the interface changes we made in hadoop-0.21 (sigh), and hence, users using the _new_ apis will have to re-compile (i.e. source compatible only). 
> Net, given that vast majority of users use the org.apache.hadoop.mapred api, it's a very reasonable way to ease migration to hadoop-2.

--
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