Mailing-List: contact yarn-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
From: Steve Loughran <stevel@hortonworks.com>
CC: "common-dev@hadoop.apache.org" <common-dev@hadoop.apache.org>,
	"mapreduce-dev@hadoop.apache.org" <mapreduce-dev@hadoop.apache.org>,
	"yarn-dev@hadoop.apache.org" <yarn-dev@hadoop.apache.org>,
	"hdfs-dev@hadoop.apache.org" <hdfs-dev@hadoop.apache.org>
Subject: Re: DISCUSS: Hadoop Compatability Guidelines
Thread-Topic: DISCUSS: Hadoop Compatability Guidelines
Thread-Index: AQHTJZr+mpwvOodlGE2wv9o0qdVBp6Km9oSAgAANrQCAAAF1gIAABz4AgAMnLwCAAAjWgA==
Date: Thu, 7 Sep 2017 18:44:52 +0000
Message-ID: <5123D471-DADA-42AF-B59B-AD1D2305D16A@hortonworks.com>
References: <302a1bbc-aa16-f6af-454b-f1304fe21be3@cloudera.com>
 <249dc210-9c6e-45d7-8852-05cc25bd9d4c@cloudera.com>
 <3F0FB138-C678-4970-BB24-DFBE58566049@hortonworks.com>
 <257a28cb-da54-1cca-2bcc-f5b31c812b19@cloudera.com>
 <CAGCyb57eavf5Y+HQ+H714bOkG8jie7m2L8XfRbhrjHgypOQRAQ@mail.gmail.com>
 <2b57eaa7-74b8-b7df-2e51-4602ed6549ba@cloudera.com>
In-Reply-To: <2b57eaa7-74b8-b7df-2e51-4602ed6549ba@cloudera.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-source-routing-agent: Processed
MIME-Version: 1.0
X-MC-Unique: lPc7ao1oP_-TT0KIkcvu0w-1
Content-Type: multipart/alternative;
	boundary="_000_5123D471DADA42AFB59BAD1D2305D16Ahortonworkscom_"
archived-at: Thu, 07 Sep 2017 18:45:04 -0000

--_000_5123D471DADA42AFB59BAD1D2305D16Ahortonworkscom_
Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable


On 7 Sep 2017, at 19:13, Daniel Templeton <daniel@cloudera.com<mailto:danie=
l@cloudera.com>> wrote:

Good point.  I think it would be valuable to enumerate the policies around =
the versioned state stores.  We have the three you listed. We should probab=
ly include the HDFS fsimage in that list.  Any others?


S3Guard now stores state in DDB. we do have a version marker & A policy wri=
tten down of how upgrades are done

https://github.com/apache/hadoop/blob/trunk/hadoop-tools/hadoop-aws/src/sit=
e/markdown/tools/hadoop-aws/s3guard.md


I also want to add a section that clarifies when it's OK to change the visi=
bility or audience of an API.

Daniel

On 9/5/17 11:04 AM, Arun Suresh wrote:
Thanks for starting this Daniel.

I think we should also add a section for store compatibility (all state
stores including RM, NM, Federation etc.). Essentially an explicit policy
detailing when is it ok to change the major and minor versions and how it
should relate to the hadoop release version.
Thoughts ?

Cheers
-Arun


On Tue, Sep 5, 2017 at 10:38 AM, Daniel Templeton <daniel@cloudera.com<mail=
to:daniel@cloudera.com>>
wrote:

Good idea.  I should have thought of that. :)  Done.

Daniel


On 9/5/17 10:33 AM, Anu Engineer wrote:

Could you please attach the PDFs to the JIRA. I think the mailer is
stripping them off from the mail.

Thanks
Anu


On 9/5/17, 9:44 AM, "Daniel Templeton" <daniel@cloudera.com<mailto:daniel@c=
loudera.com>> wrote:

Resending with a broader audience, and reattaching the PDFs.
Daniel

On 9/4/17 9:01 AM, Daniel Templeton wrote:

All, in prep for Hadoop 3 beta 1 I've been working on updating the
compatibility guidelines on HADOOP-13714.  I think the initial doc is
more or less complete, so I'd like to open the discussion up to the
broader Hadoop community.

In the new guidelines, I have drawn some lines in the sand regarding
compatibility between releases.  In some cases these lines are more
restrictive than the current practices.  The intent with the new
guidelines is not to limit progress by restricting what goes into a
release, but rather to drive release numbering to keep in line with
the reality of the code.

Please have a read and provide feedback on the JIRA.  I'm sure there
are more than a couple of areas that could be improved.  If you'd
rather not read markdown from a diff patch, I've attached PDFs of the
two modified docs.

Thanks!
Daniel


---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org<mailto:yarn-=
dev-unsubscribe@hadoop.apache.org>
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org<mailto:yar=
n-dev-help@hadoop.apache.org>


---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org<mailto:yarn-=
dev-unsubscribe@hadoop.apache.org>
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org<mailto:yar=
n-dev-help@hadoop.apache.org>


--_000_5123D471DADA42AFB59BAD1D2305D16Ahortonworkscom_--