Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (1.0)
Subject: Re: [VOTE] Release Apache Hadoop 2.7.3 RC1
From: Andrew Purtell <andrew.purtell@gmail.com>
In-Reply-To: <1471528833445.31857@hortonworks.com>
Date: Thu, 18 Aug 2016 08:47:55 -0700
Cc: Vinod Kumar Vavilapalli <vinodkv@apache.org>,
 Allen Wittenauer <aw@effectivemachines.com>,
 "common-dev@hadoop.apache.org" <common-dev@hadoop.apache.org>,
 "hdfs-dev@hadoop.apache.org" <hdfs-dev@hadoop.apache.org>,
 "yarn-dev@hadoop.apache.org" <yarn-dev@hadoop.apache.org>,
 "mapreduce-dev@hadoop.apache.org" <mapreduce-dev@hadoop.apache.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <DC215C6F-413A-47C2-94B9-564C27FF446D@gmail.com>
References: <732DB60A-844D-4FA3-822B-08DB587DEB9B@apache.org> <6192A234-0F2E-4CB4-B3C7-142728E0800A@effectivemachines.com> <A7EF3127-1DED-46F0-9AA4-A39A3F8DAC98@apache.org> <1471528833445.31857@hortonworks.com>
To: Junping Du <jdu@hortonworks.com>
archived-at: Thu, 18 Aug 2016 15:48:17 -0000

An incompatible APIs change is developer unfriendly. An incompatible behavio=
ral change is operator unfriendly. Historically, one dimension of incompatib=
ility has had a lot more mindshare than the other. It's great that this migh=
t be changing for the better.=20

Where I work when we move from one Hadoop 2.x minor to another we always spe=
nd time updating our deployment plans, alerting, log scraping, and related t=
hings due to changes. Some are debatable as if qualifying for the 'incompati=
ble' designation. I think the audit logging change that triggered this discu=
ssion is a good example of one that does. If you want to audit HDFS actions t=
hose log emissions are your API. (Inotify doesn't offer access control event=
s.) One has to code regular expressions for parsing them and reverse enginee=
r under what circumstances an audit line is emitted so you can make assumpti=
ons about what transpired. Change either and you might break someone's autom=
ation for meeting industry or legal compliance obligations. Not a trivial ma=
tter. If you don't operate Hadoop in production you might not realize the im=
plications of such a change. Glad to see Hadoop has community diversity to r=
ecognize it in some cases.=20

> On Aug 18, 2016, at 6:57 AM, Junping Du <jdu@hortonworks.com> wrote:
>=20
> I think Allen's previous comments are very misleading.=20
> In my understanding, only incompatible API (RPC, CLIs, WebService, etc.) s=
houldn't land on branch-2, but other incompatible behaviors (logs, audit-log=
, daemon's restart, etc.) should get flexible for landing. Otherwise, how co=
uld 52 issues ( https://s.apache.org/xJk5) marked with incompatible-changes c=
ould get landed on branch-2 after 2.2.0 release? Most of them are already re=
leased.=20
>=20
> Thanks,
>=20
> Junping
> ________________________________________
> From: Vinod Kumar Vavilapalli <vinodkv@apache.org>
> Sent: Wednesday, August 17, 2016 9:29 PM
> To: Allen Wittenauer
> Cc: common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org; yarn-dev@had=
oop.apache.org; mapreduce-dev@hadoop.apache.org
> Subject: Re: [VOTE] Release Apache Hadoop 2.7.3 RC1
>=20
> I always look at CHANGES.txt entries for incompatible-changes and this JIR=
A obviously wasn=E2=80=99t there.
>=20
> Anyways, this shouldn=E2=80=99t be in any of branch-2.* as committers ther=
e clearly mentioned that this is an incompatible change.
>=20
> I am reverting the patch from branch-2* .
>=20
> Thanks
> +Vinod
>=20
>> On Aug 16, 2016, at 9:29 PM, Allen Wittenauer <aw@effectivemachines.com> w=
rote:
>>=20
>>=20
>>=20
>> -1
>>=20
>> HDFS-9395 is an incompatible change:
>>=20
>> a) Why is not marked as such in the changes file?
>> b) Why is an incompatible change in a micro release, much less a minor?
>> c) Where is the release note for this change?
>>=20
>>=20
>>> On Aug 12, 2016, at 9:45 AM, Vinod Kumar Vavilapalli <vinodkv@apache.org=
> wrote:
>>>=20
>>> Hi all,
>>>=20
>>> I've created a release candidate RC1 for Apache Hadoop 2.7.3.
>>>=20
>>> As discussed before, this is the next maintenance release to follow up 2=
.7.2.
>>>=20
>>> The RC is available for validation at: http://home.apache.org/~vinodkv/h=
adoop-2.7.3-RC1/ <http://home.apache.org/~vinodkv/hadoop-2.7.3-RC0/>
>>>=20
>>> The RC tag in git is: release-2.7.3-RC1
>>>=20
>>> The maven artifacts are available via repository.apache.org <http://repo=
sitory.apache.org/> at https://repository.apache.org/content/repositories/or=
gapachehadoop-1045/ <https://repository.apache.org/content/repositories/orga=
pachehadoop-1045/>
>>>=20
>>> The release-notes are inside the tar-balls at location hadoop-common-pro=
ject/hadoop-common/src/main/docs/releasenotes.html. I hosted this at home.ap=
ache.org/~vinodkv/hadoop-2.7.3-RC1/releasenotes.html <http://people.apache.o=
rg/~vinodkv/hadoop-2.7.2-RC1/releasenotes.html> for your quick perusal.
>>>=20
>>> As you may have noted,
>>> - few issues with RC0 forced a RC1 [1]
>>> - a very long fix-cycle for the License & Notice issues (HADOOP-12893) c=
aused 2.7.3 (along with every other Hadoop release) to slip by quite a bit. T=
his release's related discussion thread is linked below: [2].
>>>=20
>>> Please try the release and vote; the vote will run for the usual 5 days.=

>>>=20
>>> Thanks,
>>> Vinod
>>>=20
>>> [1] [VOTE] Release Apache Hadoop 2.7.3 RC0: https://www.mail-archive.com=
/hdfs-dev%40hadoop.apache.org/index.html#26106 <https://www.mail-archive.com=
/hdfs-dev%40hadoop.apache.org/index.html#26106>
>>> [2]: 2.7.3 release plan: https://www.mail-archive.com/hdfs-dev%40hadoop.=
apache.org/msg24439.html <http://markmail.org/thread/6yv2fyrs4jlepmmr>
>>=20
>>=20
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
>=20
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
>=20
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>=20

---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org