Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-dev@hadoop.apache.org
Received-SPF: pass (athena.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=y64UnZHpMCLYeLyrw1/A5g+t1uZirAM5mXpLy36ZGQ68ZnlM55ptc8sR2etNx2+2DG9we+e2jMTm7xuwHkwrk53/zvq5CqxjOkTHBzhf3zczTsaDEjesScK2CQjo73kh1BCZ11HV0k4Mv1k/D4vrJbwNTiakvsn5wzXPCXD+W1w=;
References: 
 <CAJs-t7O3NVEoo3zaS8CaWikAJNZHAhbaC-zVG9+-uQO=azsffw@mail.gmail.com>
 <42382C4C8D604FFFB009C3DD5283131E@china.huawei.com>
Message-ID: <1318618688.21051.YahooMailNeo@web110704.mail.gq1.yahoo.com>
Date: Fri, 14 Oct 2011 11:58:08 -0700 (PDT)
From: Bharath Mundlapudi <bharathwork@yahoo.com>
Reply-To: Bharath Mundlapudi <bharathwork@yahoo.com>
Subject: Re: 0.23 & trunk tars,
 we'll we publishing 1 tar per component or a single tar? What about source
 tar?
To: "mapreduce-dev@hadoop.apache.org" <mapreduce-dev@hadoop.apache.org>,
  "common-dev@hadoop.apache.org" <common-dev@hadoop.apache.org>,
  "hdfs-dev@hadoop.apache.org" <hdfs-dev@hadoop.apache.org>,
  "raviteja@huawei.com" <raviteja@huawei.com>
In-Reply-To: <42382C4C8D604FFFB009C3DD5283131E@china.huawei.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
 boundary="654292850-1813074277-1318618688=:21051"

--654292850-1813074277-1318618688=:21051
Content-Type: text/plain; charset=us-ascii

Other approach would be asking which tar to build.

mapred-tar (mapred and common)
hdfs-tar (hdfs and common)
hadoop-tar (all)

In this case, hbase can just use hdfs-tar.

-Bharath


________________________________
From: Ravi Teja <raviteja@huawei.com>
To: mapreduce-dev@hadoop.apache.org; common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org
Sent: Wednesday, October 12, 2011 9:43 PM
Subject: RE: 0.23 & trunk tars, we'll we publishing 1 tar per component or a single tar? What about source tar?

I feel #4 as a better option.

Regards,
Ravi Teja

-----Original Message-----
From: Alejandro Abdelnur [mailto:tucu@cloudera.com] 
Sent: Wednesday, October 12, 2011 9:38 PM
To: common-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org;
hdfs-dev@hadoop.apache.org
Subject: 0.23 & trunk tars, we'll we publishing 1 tar per component or a
single tar? What about source tar?

Currently common, hdfs and mapred create partial tars which are not usable
unless they are stitched together into a single tar.

With HADOOP-7642 the stitching happens as part of the build.

The build currently produces the following tars:

1* common TAR
2* hdfs (partial) TAR
3* mapreduce (partial) TAR
4* hadoop (full, the stitched one) TAR

#1 on its own does not run anything, #2 and #3 on their own don't run. #4
runs hdfs & mapreduce.

Questions:

Q1. Does it make sense to publish #1, #2 & #3? Or #4 is sufficient and you
start the services you want (i.e. Hbase would just use HDFS)?

Q2. And what about a source TAR, does it make sense to have source TAR per
component or a single TAR for the whole?


For simplicity (for the build system and for users) I'd prefer a single
binary TAR and a single source TAR.

Thanks.

Alejandro
--654292850-1813074277-1318618688=:21051--