Mailing-List: contact mapreduce-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-dev@hadoop.apache.org
Received-SPF: pass (nike.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type;
  b=j6VurKx1x8OdqRcUh9Km/2F5qSJc6pG/tszewW0aRpWw/0a59IsxrprmCYcWhVJiPXjczP+23L8o4oOPseh25XkSJSy3d3TQeEt/UQ38f6SVjqQEC+XG8kzlxQ/PO7vv33WrBY7Y/JjLYayWun0cFa1RiNXHdIxeD/xe03+MMRQ=;
References: 
 <CADY20s75nsCFEpNqaT5YcuW9yUp_sKnfiJF1zKk8p2-YUZThfg@mail.gmail.com>
 <CA7D1986.334B6%amarsri@yahoo-inc.com>
 <CAJs-t7P_cXtXMQ7-+n9wrMT_dk8+2MC=pRnJfx2wNf4gW3bE9Q@mail.gmail.com>
 <CANJr2=Hj77FbXOvRwu0Xb7HiMFwqgLBHqP4gcrBskTcc4R6LbA@mail.gmail.com>
Message-ID: <1314362710.61210.YahooMailNeo@web44714.mail.sp1.yahoo.com>
Date: Fri, 26 Aug 2011 05:45:10 -0700 (PDT)
From: Mithun Radhakrishnan <mithun.radhakrishnan@yahoo.com>
Reply-To: Mithun Radhakrishnan <mithun.radhakrishnan@yahoo.com>
Subject: Re: DistCpV2 in 0.23
To: "mapreduce-dev@hadoop.apache.org" <mapreduce-dev@hadoop.apache.org>
In-Reply-To: 
 <CANJr2=Hj77FbXOvRwu0Xb7HiMFwqgLBHqP4gcrBskTcc4R6LbA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1685908452-1314362710=:61210"

--0-1685908452-1314362710=:61210
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Would it be acceptable if retooling of tools/ were taken up separately? It =
sounds to me like this might be a distinct (albeit related) task.=0A=0AMith=
un=0A=0A=0A________________________________=0AFrom: Giridharan Kesavan <gke=
savan@hortonworks.com>=0ATo: mapreduce-dev@hadoop.apache.org=0ASent: Friday=
, August 26, 2011 12:04 PM=0ASubject: Re: DistCpV2 in 0.23=0A=0A+1 to Aleja=
ndro's=0A=0AI prefer to keep the hadoop-tools at trunk level.=0A=0A-Giri=0A=
=0AOn Thu, Aug 25, 2011 at 9:15 PM, Alejandro Abdelnur <tucu@cloudera.com> =
wrote:=0A> I'd suggest putting hadoop-tools either at trunk/ level or havin=
g a a tools=0A> aggregator module for hdfs and other for common.=0A>=0A> I =
personal would prefer at trunk/.=0A>=0A> Thanks.=0A>=0A> Alejandro=0A>=0A> =
On Thu, Aug 25, 2011 at 9:06 PM, Amareshwari Sri Ramadasu <=0A> amarsri@yah=
oo-inc.com> wrote:=0A>=0A>> Agree. It should be separate maven module (and =
patch puts it as separate=0A>> maven module now). And top level for hadoop =
tools is nice to have, but it=0A>> becomes hard to maintain until patch aut=
omation tests run the tests under=0A>> tools. Currently we see many times t=
he changes in HDFS effecting RAID tests=0A>> in MapReduce. So, I'm fine put=
ting the tools under hadoop-mapreduce.=0A>>=0A>> I propose we can have some=
thing like the following:=0A>>=0A>> trunk/=0A>> =A0- hadoop-mapreduce=0A>> =
=A0 =A0 =A0- hadoop-mr-client=0A>> =A0 =A0 =A0- hadoop-yarn=0A>> =A0 =A0 =
=A0- hadoop-tools=0A>> =A0 =A0 =A0 =A0 =A0- hadoop-streaming=0A>> =A0 =A0 =
=A0 =A0 =A0- hadoop-archives=0A>> =A0 =A0 =A0 =A0 =A0- hadoop-distcp=0A>>=
=0A>> Thoughts?=0A>>=0A>> @Eli and @JD, we did not replace old legacy distc=
p because this is really a=0A>> complete rewrite and did not want to remove=
 it until users are familiarized=0A>> with new one.=0A>>=0A>> On 8/26/11 12=
:51 AM, "Todd Lipcon" <todd@cloudera.com> wrote:=0A>>=0A>> Maybe a separate=
 toplevel for hadoop-tools? Stuff like RAID could go=0A>> in there as well =
- ie tools that are downstream of MR and/or HDFS.=0A>>=0A>> On Thu, Aug 25,=
 2011 at 12:09 PM, Mahadev Konar <mahadev@hortonworks.com>=0A>> wrote:=0A>>=
 > +1 for a seperate module in hadoop-mapreduce-project. I think=0A>> > had=
oop-mapreduce-client might not be right place for it. We might have=0A>> > =
to pick a new maven module under hadoop-mapreduce-project that could=0A>> >=
 host streaming/distcp/hadoop archives.=0A>> >=0A>> > thanks=0A>> > mahadev=
=0A>> >=0A>> > On Thu, Aug 25, 2011 at 11:04 AM, Alejandro Abdelnur <tucu@c=
loudera.com>=0A>> wrote:=0A>> >> Agree, it should be a separate maven modul=
e.=0A>> >>=0A>> >> And it should be under hadoop-mapreduce-client, right?=
=0A>> >>=0A>> >> And now that we are in the topic, the same should go for s=
treaming, no?=0A>> >>=0A>> >> Thanks.=0A>> >>=0A>> >> Alejandro=0A>> >>=0A>=
> >> On Thu, Aug 25, 2011 at 10:58 AM, Todd Lipcon <todd@cloudera.com>=0A>>=
 wrote:=0A>> >>=0A>> >>> On Thu, Aug 25, 2011 at 10:36 AM, Eli Collins <eli=
@cloudera.com>=0A>> wrote:=0A>> >>> > Nice work! =A0 I definitely think thi=
s should go in 23 and 20x.=0A>> >>> >=0A>> >>> > Agree with JD that it shou=
ld be in the core code, not contrib. =A0If=0A>> >>> > it's going to be main=
tained then we should put it in the core code.=0A>> >>>=0A>> >>> Now that w=
e're all mavenized, though, a separate maven module and=0A>> >>> artifact d=
oes make sense IMO - ie "hadoop jar=0A>> >>> hadoop-distcp-0.23.0-SNAPSHOT"=
 rather than "hadoop distcp"=0A>> >>>=0A>> >>> -Todd=0A>> >>> --=0A>> >>> T=
odd Lipcon=0A>> >>> Software Engineer, Cloudera=0A>> >>>=0A>> >>=0A>> >=0A>=
>=0A>>=0A>>=0A>> --=0A>> Todd Lipcon=0A>> Software Engineer, Cloudera=0A>>=
=0A>>=0A>=0A=0A=0A=0A-- =0A-Giri
--0-1685908452-1314362710=:61210--