Review request for HADOOP-11875

Hi YARN and MapReduce developers, I'm working for Java 9 support and created a patch to replace '_' with '__' in the hamlet framework (org.apache.hadoop.yarn.webapp.hamlet) used by YARN and MapReduce webapp. In Java 9 '_' as a one-character identifier is banned.

[jira] [Reopened] (MAPREDUCE-6824) TaskAttemptImpl#createCommonContainerLaunchContext is longer than 150 lines

[ https://issues.apache.org/jira/browse/MAPREDUCE-6824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka reopened MAPREDUCE-6824: -- Reopen this to run precommit job for branch-2 >

Re: Upgrading minimum version of Maven to 3.1 from 3.0

Agreed to upgrade to 3.3+ and change the version only in trunk. -Akira On 2017/04/05 11:21, Sunil G wrote: Thanks Akira and Junping. @Junping. Yes, we plan to change this only in trunk and new YARN UI is available there. I also feel that there is no issue in moving to a latest version such as

Re: Upgrading minimum version of Maven to 3.1 from 3.0

Thanks Akira and Junping. @Junping. Yes, we plan to change this only in trunk and new YARN UI is available there. I also feel that there is no issue in moving to a latest version such as 3.3. + Sunil On Tue, Apr 4, 2017 at 11:35 PM Junping Du wrote: > Thanks Sunil to

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

For more details, see https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/366/ [Apr 3, 2017 2:35:09 PM] (weichiu) HDFS-11515. -du throws ConcurrentModificationException. Contributed by [Apr 3, 2017 2:57:28 PM] (weichiu) HDFS-11598. Improve -setrep for Erasure Coded files.

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

For more details, see https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/278/ [Apr 3, 2017 2:35:09 PM] (weichiu) HDFS-11515. -du throws ConcurrentModificationException. Contributed by [Apr 3, 2017 2:57:28 PM] (weichiu) HDFS-11598. Improve -setrep for Erasure Coded files.

Re: Upgrading minimum version of Maven to 3.1 from 3.0

Thanks Sunil to bring it up. However, any reason not to go to latest version of maven (3.3+)? Even version 3.1 is quite old - released 3+ years from now (please refer: https://archive.apache.org/dist/maven/binaries/). btw, I assume we only plan to change maven version on trunk given new YARN UI