Re: [VOTE] Release Apache Hadoop 2.7.3 RC1

gt;     > Junping     >     > From: Vinod Kumar Vavilapalli <vino...@apache.org>     > Sent: Wednesday, August 17, 2016 9:29 PM     > To: Allen Wittenauer     > Cc: common-...@hadoop.apache.org; hdfs-...@hadoop.apache.org; yarn-...@hadoop.apa

Re: [VOTE] Release Apache Hadoop 2.7.3 RC1

ded on branch-2 after 2.2.0 release? Most > of them are already released. > > > > Thanks, > > > > Junping > > ________ > > From: Vinod Kumar Vavilapalli <vino...@apache.org> > > Sent:

Re: [VOTE] Release Apache Hadoop 2.7.3 RC1

t; From: Vinod Kumar Vavilapalli <vino...@apache.org> > Sent: Wednesday, August 17, 2016 9:29 PM > To: Allen Wittenauer > Cc: common-...@hadoop.apache.org; hdfs-...@hadoop.apache.org; yarn-...@hadoop.apache.org; mapreduce-dev@hadoop.apache.org > Subject: Re: [VO

Re: [VOTE] Release Apache Hadoop 2.7.3 RC1

I believe it was described as some previous audit entries have been superseded by new ones and that the order may no longer be the same for other entries. For what it’s worth, I agree with the assertion that this is a backward incompatible output - especially for audit logs. On Thu, Aug 18, 2016

Re: [VOTE] Release Apache Hadoop 2.7.3 RC1

doop.apache.org; mapreduce-dev@hadoop.apache.org > Subject: Re: [VOTE] Release Apache Hadoop 2.7.3 RC1 > > I always look at CHANGES.txt entries for incompatible-changes and this JIRA > obviously wasn’t there. > > Anyways, this shouldn’t be in any of branch-2.* as committers there clear

Re: [VOTE] Release Apache Hadoop 2.7.3 RC1

> On 18 Aug 2016, at 14:57, Junping Du wrote: > > I think Allen's previous comments are very misleading. > In my understanding, only incompatible API (RPC, CLIs, WebService, etc.) > shouldn't land on branch-2, but other incompatible behaviors (logs, > audit-log,

Re: [VOTE] Release Apache Hadoop 2.7.3 RC1

:29 PM To: Allen Wittenauer Cc: common-...@hadoop.apache.org; hdfs-...@hadoop.apache.org; yarn-...@hadoop.apache.org; mapreduce-dev@hadoop.apache.org Subject: Re: [VOTE] Release Apache Hadoop 2.7.3 RC1 I always look at CHANGES.txt entries for incompatible-changes and this JIRA obviously

Re: [VOTE] Release Apache Hadoop 2.7.3 RC1

Canceling the release vote for this and other issues reported. +Vinod > On Aug 16, 2016, at 10:01 PM, Akira Ajisaka > wrote: > > -1 (binding) > > HADOOP-13434 and HADOOP-11814, committed between RC0 and RC1, are not > reflected in the release note. > > -Akira >

Re: [VOTE] Release Apache Hadoop 2.7.3 RC1

I always look at CHANGES.txt entries for incompatible-changes and this JIRA obviously wasn’t there. Anyways, this shouldn’t be in any of branch-2.* as committers there clearly mentioned that this is an incompatible change. I am reverting the patch from branch-2* . Thanks +Vinod > On Aug 16,

RE: [VOTE] Release Apache Hadoop 2.7.3 RC1

[mailto:j...@hortonworks.com] Sent: 17 August 2016 18:45 To: Allen Wittenauer; common-...@hadoop.apache.org; kshu...@yahoo-inc.com; kih...@yahoo-inc.com Cc: hdfs-...@hadoop.apache.org; yarn-...@hadoop.apache.org; mapreduce-dev@hadoop.apache.org Subject: Re: [VOTE] Release Apache Hadoop 2.7.3 RC1

Re: [VOTE] Release Apache Hadoop 2.7.3 RC1

gust 17, 2016 5:29 AM > To: common-...@hadoop.apache.org > Cc: hdfs-...@hadoop.apache.org; yarn-...@hadoop.apache.org; > mapreduce-dev@hadoop.apache.org > Subject: Re: [VOTE] Release Apache Hadoop 2.7.3 RC1 > > -1 > > HDFS-9395 is an incompatible change: > > a) Why is not marked as s

Re: [VOTE] Release Apache Hadoop 2.7.3 RC1

-1 (binding) HADOOP-13434 and HADOOP-11814, committed between RC0 and RC1, are not reflected in the release note. -Akira On 8/17/16 13:29, Allen Wittenauer wrote: -1 HDFS-9395 is an incompatible change: a) Why is not marked as such in the changes file? b) Why is an incompatible change

Re: [VOTE] Release Apache Hadoop 2.7.3 RC1

-1 HDFS-9395 is an incompatible change: 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? > On Aug 12, 2016, at 9:45 AM, Vinod Kumar Vavilapalli >

Re: [VOTE] Release Apache Hadoop 2.7.3 RC1

Thanks Steve, this is one area that isn’t very well release-tested usually! +Vinod > On Aug 16, 2016, at 2:25 AM, Steve Loughran wrote: > > I've just looked at the staged JARs and how they worked with downstream apps > —that being a key way that Hadoop artifacts are

Re: [VOTE] Release Apache Hadoop 2.7.3 RC1

+1 binding 1. built and tested apache slider (incubating) against the Hadoop 2.7.3 artifacts 2. did a build & test of Apache Spark master branch iwth 2.7.3 JARs, For that I had to tweak spark's build to support the staging repo; hopefully that will get into Spark

Re: [VOTE] Release Apache Hadoop 2.7.3 RC1

.apache.org>; hdfs-...@hadoop.apache.org; yarn-...@hadoop.apache.org; "mapreduce-dev@hadoop.apache.org" <mapreduce-dev@hadoop.apache.org> Cc: Vinod Kumar Vavilapalli <vino...@apache.org> Sent: Friday, August 12, 2016 11:45 AM Subject: [VOTE] Release Apache Hadoop 2.7.3 RC1 H

Re: [VOTE] Release Apache Hadoop 2.7.3 RC1

Thanks Marco. It was a Thursday late-night slip-up. Fixed the dates and replaced the bits, so the voting can continue. FYI, they aren’t binding though - as it all depends on how the release voting goes. One should usually only trust the release-date published on the website. Thanks +Vinod >

Re: [VOTE] Release Apache Hadoop 2.7.3 RC1

Hi Vinod, I'm not sure if this is relevant, but you changed the release date in the CHANGES.txt files to 2016-09-19. I guess you have meant 2016-08-19. See:

[VOTE] Release Apache Hadoop 2.7.3 RC1

Hi all, I've created a release candidate RC1 for Apache Hadoop 2.7.3. As discussed before, this is the next maintenance release to follow up 2.7.2. The RC is available for validation at: http://home.apache.org/~vinodkv/hadoop-2.7.3-RC1/ The