hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erik Krogen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-7118) Distributed cache conflicts breaks backwards compatability
Date Tue, 24 Jul 2018 16:17:00 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-7118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16554470#comment-16554470
] 

Erik Krogen commented on MAPREDUCE-7118:
----------------------------------------

[~leftnoteasy], we should put this in branch-3.0 as well, right?

> 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
>             Fix For: 3.2.0, 3.1.1
>
>         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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-help@hadoop.apache.org


Mime
View raw message