[
https://issues.apache.org/jira/browse/MAPREDUCE-7118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16549891#comment-16549891
]
Hudson commented on MAPREDUCE-7118:
-----------------------------------
FAILURE: Integrated in Jenkins build Hadoop-trunk-Commit #14596 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/14596/])
MAPREDUCE-7118. Distributed cache conflicts breaks backwards (wangda: rev
b3b4d4ccb53fdf8dacc66e912822b34f8b3bf215)
* (edit)
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/main/java/org/apache/hadoop/mapreduce/v2/util/LocalResourceBuilder.java
* (edit)
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/test/java/org/apache/hadoop/mapreduce/v2/util/TestMRApps.java
> Distributed cache conflicts breaks backwards compatability
> ----------------------------------------------------------
>
> Key: MAPREDUCE-7118
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-7118
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 3.0.0, 3.1.0, 3.2.0
> Reporter: Jason Lowe
> Assignee: Jason Lowe
> Priority: Blocker
> Attachments: MAPREDUCE-7118.001.patch
>
>
> MAPREDUCE-4503 made distributed cache conflicts break job submission, but
> this was quickly downgraded to a warning in MAPREDUCE-4549. Unfortunately
> the latter did not go into trunk, so the fix is only in 0.23 and 2.x. When
> Oozie, Pig, and other downstream projects that can occasionally generate
> distributed cache conflicts move to Hadoop 3.x the workflows that used to
> work on 0.23 and 2.x no longer function.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
