[jira] [Created] (HADOOP-11878) NPE in FileContext.java # fixRelativePart(Path p)

Brahma Reddy Battula created HADOOP-11878: - Summary: NPE in FileContext.java # fixRelativePart(Path p) Key: HADOOP-11878 URL: https://issues.apache.org/jira/browse/HADOOP-11878 Project: Hadoop

Build failed in Jenkins: Hadoop-common-trunk-Java8 #178

See Changes: [kasha] YARN-3464. Race condition in LocalizerRunner kills localizer before localizing all resources. (Zhihai Xu via kasha) [aw] HADOOP-11865. Incorrect path mentioned in document for accessing script files (J.A

[jira] [Created] (HADOOP-11879) Typo in mapreduce tutorial

John Michael Luy created HADOOP-11879: - Summary: Typo in mapreduce tutorial Key: HADOOP-11879 URL: https://issues.apache.org/jira/browse/HADOOP-11879 Project: Hadoop Common Issue Type: Im

[jira] [Created] (HADOOP-11880) aw jira sub-task testing, ignore

Allen Wittenauer created HADOOP-11880: - Summary: aw jira sub-task testing, ignore Key: HADOOP-11880 URL: https://issues.apache.org/jira/browse/HADOOP-11880 Project: Hadoop Common Issue Ty

[jira] [Created] (HADOOP-11881) test-patch.sh javac warning code is wildly wrong

Allen Wittenauer created HADOOP-11881: - Summary: test-patch.sh javac warning code is wildly wrong Key: HADOOP-11881 URL: https://issues.apache.org/jira/browse/HADOOP-11881 Project: Hadoop Common

[jira] [Created] (HADOOP-11882) Audit all of the findbugs excludes

Allen Wittenauer created HADOOP-11882: - Summary: Audit all of the findbugs excludes Key: HADOOP-11882 URL: https://issues.apache.org/jira/browse/HADOOP-11882 Project: Hadoop Common Issue

Re: [DISCUSS] Release numbering for stable 2.8 and beyond

I think Karthik correctly identified the two reasons we might want to denote a release as "unstable": a) Compatibility. Whether we have freedom to break compatibility before the final release, i.e. what "alpha" typically means. b) Quality. As Konst says, a release can be allowed to break compatib

Re: [DISCUSS] Release numbering for stable 2.8 and beyond

My understanding was that the main reason that we labeled 2.0 alpha and 2.1 beta is that we wanted flexibility to make breaking API changes. Is that the case now with 2.7? I.e. do we have APIs labeled as Public / Stable that we want freedom to change in 2.8? If not, I definitely don't think the

Planning Hadoop 2.6.1 release

There were several requests on the user lists [1] for a 2.6.1 release. I got many offline comments too. Planning to do a 2.6.1 release in a few weeks time. We already have a bunch of tickets committed to 2.7.1. I created a filter [2] to tracking pending tickets. We need to collectively come up wi

[jira] [Reopened] (HADOOP-11869) checkstyle rules/script need re-visiting

[ https://issues.apache.org/jira/browse/HADOOP-11869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sidharta Seethana reopened HADOOP-11869: I am re-opening this issue because the scope of this JIRA is different. > checkstyle

[jira] [Created] (HADOOP-11883) Checkstyle Results are Different Between Command Line and Eclipse

Jonathan Eagles created HADOOP-11883: Summary: Checkstyle Results are Different Between Command Line and Eclipse Key: HADOOP-11883 URL: https://issues.apache.org/jira/browse/HADOOP-11883 Project:

Build failed in Jenkins: Hadoop-common-trunk-Java8 #179

See Changes: [devaraj] MAPREDUCE-6252. JobHistoryServer should not fail when encountering a [ozawa] MAPREDUCE-6341. Fix typo in mapreduce tutorial. Contributed by John Michael Luy. [xgong] YARN-3530. ATS throws exception on