Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-dev@hadoop.apache.org
Subject: Re: hadoop-hdfs-client splitoff is going to break code
MIME-Version: 1.0
From: Steve Loughran <stevel@hortonworks.com>
To: "common-dev@hadoop.apache.org" <common-dev@hadoop.apache.org>
CC: "hdfs-dev@hadoop.apache.org" <hdfs-dev@hadoop.apache.org>
Thread-Topic: hadoop-hdfs-client splitoff is going to break code
Thread-Index: AQHRBqbtCj8cwWlN80+euZfCB1F8855zytSAgADMLYA=
Date: Tue, 20 Oct 2015 09:12:46 +0000
Message-ID: <99B01FB8-A9CD-4C5D-8D9A-1226C19FF244@hortonworks.com>
References: <8E19C6FE-9EDF-4199-BA4F-DDDD547FAF85@hortonworks.com>
 <CA+qbEUO-BCp9wcc3dEKhBUxU-3amimY-9TTFu7Kyz9r132UJDQ@mail.gmail.com>
In-Reply-To: 
 <CA+qbEUO-BCp9wcc3dEKhBUxU-3amimY-9TTFu7Kyz9r132UJDQ@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-ID: <298172235B07DB44A9ED1B4EAF0D34F5@exch080.serverpod.net>
Content-Transfer-Encoding: quoted-printable


> On 19 Oct 2015, at 22:01, Colin P. McCabe <cmccabe@apache.org> wrote:
>=20
> Thanks for being proactive here, Steve.

no, just building downstream things. Caught a failure of spark to build aga=
inst trunk too, but that's a one liner to import the no-deprecated Auth Exc=
eption

>  I think this is a good example of
> why this change should have been done in a branch rather than having been
> done directly in trunk.

Given the size of the change, I'm now convincedt that yes, the hadoop-clien=
t split should have been in a branch. What it offers there is the ability t=
o choose when to merge in. As it is, any Hadoop 2.8 release will have this =
feature. It's going to be visible, and that's going to add more testing. We=
 should expect this to cause things to surface in the release process. We a=
lso need to consider what's going to be the policy if 2.8.0 turns out to br=
eak something: what are we prepared to roll back?