Mailing-List: contact general-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@hadoop.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1082.1)
Subject: Re: Hadoop 0.22 update
From: Devaraj Das <ddas@hortonworks.com>
In-Reply-To: 
 <CAPn_vTtC5EiCDfQ4BBMs1yScgGxOrEke9jeYUSe=eGD7C-kDUw@mail.gmail.com>
Date: Tue, 2 Aug 2011 13:07:48 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <68181C14-A504-40E9-B890-CF3CAB8FBC34@hortonworks.com>
References: <41155200-3690-4344-9EA6-6A57F72E19DE@mac.com>
 <CA5D98B4.DEE%Milind.Bhandarkar@emc.com>
 <CAPn_vTvF=bmcsvuC_-BZUj_LF+y=by_ssYTw0Ygh=tDmdrxeoQ@mail.gmail.com>
 <CAPn_vTtC5EiCDfQ4BBMs1yScgGxOrEke9jeYUSe=eGD7C-kDUw@mail.gmail.com>
To: general@hadoop.apache.org

+1 to removing the TaskController code for the 0.22 release.

In the MR-279 branch, the security issues identified in MAPREDUCE-2178 =
have been taken care of (to my knowledge).=20

On Aug 2, 2011, at 12:58 PM, Eli Collins wrote:

> On Tue, Aug 2, 2011 at 12:25 PM, Eli Collins <eli@cloudera.com> wrote:
>> On Tue, Aug 2, 2011 at 12:19 PM,  <Milind.Bhandarkar@emc.com> wrote:
>>> Having talked to various folks in the community about their =
willingness to
>>> stabilize and use 0.22 and make it production-quality, here is what =
I
>>> propose:
>>>=20
>>> 1. Cut a release 0.22.0 without mapreduce-2178 patch, with
>>> hadoop.security.authentication set to simple (I.e. No =
authentication).
>>> Make sure that MR-2178 is highlighted as known-issue in the =
top-level dir
>>> (create a KNOWN-ISSUES.txt ?), and carry out a vote.
>>>=20
>>> 2. Later, when MR-2178 patch is committed, cut a release for 0.22.1. =
(I
>>> have heard of folks working on it, but no date commitments yet.)
>>>=20
>>> The reason a 0.22.0 release should happen, IMHO, even without =
MR-2178, is
>>> that the other components of Hadoop stack (e.g. Pig, hbase, hive =
etc) will
>>> have a release to test against, and fix any issues for =
incompatibility.
>>> Also, for folks who do not use kerberos authentication (>90% of the =
hadoop
>>> users, to my knowledge), it will be a release closest to trunk, with =
HDFS
>>> appends. Plus, any issues found in the HDFS part of the release =
would be
>>> directly applicable to the trunk and other future releases. (Not so =
about
>>> map-reduce, which will undergo major surgery in trunk because of =
MR-279.)
>>>=20
>>> Thoughts ?
>>>=20
>>=20
>> Sounds reasonable to me.  #1 is what we did for the 0.21 release.
>=20
> Actually, I didn't read close enough. For 0.21 we actually removed the
> task tracker, think it makes sense to do that here as well.
>=20
> Thanks,
> Eli