Apache Hadoop qbt Report: trunk+JDK8 on Linux/ppc64le

2017-05-12 Thread Apache Jenkins Server
For more details, see https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/312/ [May 11, 2017 6:03:45 PM] (brahma) HADOOP-14410. Correct spelling of 'beginning' and variants. Contributed [May 11, 2017 7:06:06 PM] (templedf) HADOOP-14413. Add Javadoc comment for jitter parameter on [M

Re: About 2.7.4 Release

2017-05-12 Thread Konstantin Shvachko
Latest update on the links and filters. Here is the correct link for the filter: https://issues.apache.org/jira/secure/IssueNavigator.jspa?requestId=12340814 Also updated: https://s.apache.org/Dzg4 Had to do some Jira debugging. Sorry for confusion. Thanks, --Konstantin On Wed, May 10, 2017 at

Apache Hadoop qbt Report: trunk+JDK8 on Linux/x86

2017-05-12 Thread Apache Jenkins Server
For more details, see https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/401/ [May 11, 2017 6:03:45 PM] (brahma) HADOOP-14410. Correct spelling of 'beginning' and variants. Contributed [May 11, 2017 7:06:06 PM] (templedf) HADOOP-14413. Add Javadoc comment for jitter parameter on [M

[jira] [Created] (HADOOP-14417) Update cipher list for KMS

2017-05-12 Thread John Zhuge (JIRA)
John Zhuge created HADOOP-14417: --- Summary: Update cipher list for KMS Key: HADOOP-14417 URL: https://issues.apache.org/jira/browse/HADOOP-14417 Project: Hadoop Common Issue Type: Improvement

[jira] [Created] (HADOOP-14416) Path not resolving correctly while authorizing with WASB-Ranger when it starts with 'wasb:///' (triple-slash)

2017-05-12 Thread Sivaguru Sankaridurg (JIRA)
Sivaguru Sankaridurg created HADOOP-14416: - Summary: Path not resolving correctly while authorizing with WASB-Ranger when it starts with 'wasb:///' (triple-slash) Key: HADOOP-14416 URL: https://issues.apac

understanding hadoop.tmp.dir

2017-05-12 Thread Steve Loughran
I've been looking for a location on HDFS for temp data as part of HADOOP-13786, which has had me looking at hadoop.tmp.dir 1. There's no actual java constant for it 2. We don't spell out that it is in the local FS only...there's a risk that it is picked up and used in the cluster path, w