[
https://issues.apache.org/jira/browse/HADOOP-8358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-8358:
Resolution: Fixed
Fix Version/s: 2.0.1-alpha
Target Version/s: (was: 2.0.1-alpha, 3.0.0)
[
https://issues.apache.org/jira/browse/HADOOP-8358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-8358:
Attachment: HADOOP-8358.patch
Rebased the core-site.xml changes that caused the patch application to fail.
[
https://issues.apache.org/jira/browse/HADOOP-8358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-8358:
Target Version/s: 2.0.1-alpha, 3.0.0 (was: 2.0.0-alpha, 3.0.0)
> Config-related WARN for dfs.web.ugi
[
https://issues.apache.org/jira/browse/HADOOP-8358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-8358:
Attachment: HADOOP-8358.patch
Resubmitting patch pre-commit just to be sure about the Findbugs initializat
[
https://issues.apache.org/jira/browse/HADOOP-8358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-8358:
Attachment: HADOOP-8358.patch
This patch is in HADOOP cause its slightly wide/crossproject. Lemme know if
[
https://issues.apache.org/jira/browse/HADOOP-8358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-8358:
Assignee: Harsh J
Target Version/s: 2.0.0, 3.0.0 (was: 3.0.0, 2.0.0)
Status: Pat