Mailing-List: contact mapreduce-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-dev@hadoop.apache.org
Received-SPF: pass (athena.apache.org: domain of eli@cloudera.com designates
 74.125.82.176 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <0B729182-FF41-480D-ACFA-7F3917ABDB27@hortonworks.com>
References: 
 <CAPn_vTsdiiqfCB2G0HfsOr3W_4PKoocPcTf2VB93Y3MZrzRczQ@mail.gmail.com>
	<0163F206-AB23-48D5-B258-9ADD79E90498@hortonworks.com>
	<F48B62D1-0265-406D-852D-5291A9A1ED66@hortonworks.com>
	<CAPn_vTu+G1KgfMPRW352qbrHqoY-0QVbPXh2OuHVz2U=a0jEzA@mail.gmail.com>
	<0B729182-FF41-480D-ACFA-7F3917ABDB27@hortonworks.com>
Date: Wed, 13 Jul 2011 15:08:28 -0700
Message-ID: 
 <CAPn_vTu+hMq6ai-CRr+KWST_v+a97OqV6=OuD7vKuRj277Z5KQ@mail.gmail.com>
Subject: Re: MR1 next steps
From: Eli Collins <eli@cloudera.com>
To: mapreduce-dev@hadoop.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Wed, Jul 13, 2011 at 2:52 PM, Arun C Murthy <acm@hortonworks.com> wrote:
>
> On Jul 13, 2011, at 10:31 AM, Eli Collins wrote:
>>
>> Combining with the MR2 merge makes sense to me.
>>
>> Aside from o.a.h.m.server, what would be removed? Seems like parts of
>> src/contrib no longer apply =A0(eg fs scheduler) =A0and others (gridmix,
>> raid) should be able to continue to work.
>
> Good point. Maybe we should do it post merge since we need to evaluate im=
plications on contrib stuff aprior.

You're right, let's not gate the MR2 merge on MR1 removal.

It's been a week since the thread started so if no one objects I'll
start a thread on general@.

Thanks,
Eli