[VOTE] Release Apache Hadoop 2.7.3 RC2

2016-08-17 Thread Vinod Kumar Vavilapalli
Hi all, I've created a new release candidate RC2 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-RC2/

Re: [VOTE] Release Apache Hadoop 2.7.3 RC1

2016-08-17 Thread Vinod Kumar Vavilapalli
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

2016-08-17 Thread Vinod Kumar Vavilapalli
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,

[jira] [Created] (MAPREDUCE-6759) JobSubmitter/JobResourceUploader should parallelize upload of -libjars, -files, -archives

2016-08-17 Thread Dennis Huo (JIRA)
Dennis Huo created MAPREDUCE-6759: - Summary: JobSubmitter/JobResourceUploader should parallelize upload of -libjars, -files, -archives Key: MAPREDUCE-6759 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6759

RE: [VOTE] Release Apache Hadoop 2.7.3 RC1

2016-08-17 Thread Balkrushna Patil
Hi all, I want to go dipper in mapreduce source code so I have to embed that code in IDE. Can anybody tell me from where I should have to download source code. Thanks and Regards Balkrushna Patil augmentIQ Data Sciences Pvt Ltd. Mob: +91-9766 4996 81 -Original Message- From: Junping Du

Re: [VOTE] Release Apache Hadoop 2.7.3 RC1

2016-08-17 Thread Allen Wittenauer
Touching the audit log is *extremely* dangerous from a compatibility perspective. It is easily the most machine processed log in Hadoop (with the second likely being the fsck log). In particular, this comment tells me that we are almost certainly going to break users: "Some