Mailing-List: contact general-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@hadoop.apache.org
Received-SPF: pass (athena.apache.org: domain of harsh@cloudera.com designates
 209.85.213.176 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <A72BC5CA-3AFF-429C-B59B-24269D88F172@hortonworks.com>
References: <9FE3E432-DB18-4284-BE82-ECF300A2E7B4@hortonworks.com>
 <ED8063F4-2BF3-4B51-A89F-FC5784A6D133@cloudera.com>
 <4ECB7AD2.2090902@apache.org>
 <A72BC5CA-3AFF-429C-B59B-24269D88F172@hortonworks.com>
From: Harsh J <harsh@cloudera.com>
Date: Wed, 23 Nov 2011 07:47:52 +0530
Message-ID: 
 <CAOcnVr1FbQMqDERZNH6qqoAe-6EqjXD_E5HLPWbjG0X876OHig@mail.gmail.com>
Subject: Re: Un-deprecate 'old' MR apis in branch-0.23
To: general@hadoop.apache.org
Content-Type: text/plain; charset=ISO-8859-1

I'm +1 as long as the goal is still to eventually transition to a
single, supported API over upcoming releases. We can go over 1:1
guarantees over a JIRA perhaps, to evaluate if any library work still
needs to be done.

On Wed, Nov 23, 2011 at 3:30 AM, Arun C Murthy <acm@hortonworks.com> wrote:
>
> On Nov 22, 2011, at 2:34 AM, Steve Loughran wrote:
>
>> On 22/11/11 02:18, Harsh J wrote:
>>> Are gonna be maintaining both APIs forever?
>>
>>
>> That's a key point. Either there are two apis forever or, some time after the new APIs are both a proper superset of the old APIs (are we there yet?) and the majority of downstream project have migrated to the new APIs, then the old ones can be removed.
>>
>> And how do you persuade developers to move off the old APIs except through deprecation warnings?
>>
>
> It isn't clear, yet, if the new apis are a proper superset of the old APIs i.e. only in 0.21 did they come close to completion (added new Cluster apis etc.).
>
> As a result, with very little exposure, it's hard to mark them as 'stable' yet. Hence, my proposal to keep the old apis as stable and new one as evolving for hadoop-0.23.
>
> Furthermore, my personal preference would be to further tweak the new apis along the lines of https://issues.apache.org/jira/browse/MAPREDUCE-1183 before we declare them stable (that has real benefits for Pig/Hive etc.), but that is some way away.
>
> Arun


-- 
Harsh J