You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Alejandro Abdelnur (JIRA)" <ji...@apache.org> on 2012/12/11 20:51:22 UTC
[jira] [Comment Edited] (MAPREDUCE-4549) Distributed cache
conflicts breaks backwards compatability
[ https://issues.apache.org/jira/browse/MAPREDUCE-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13529263#comment-13529263 ]
Alejandro Abdelnur edited comment on MAPREDUCE-4549 at 12/11/12 7:51 PM:
-------------------------------------------------------------------------
Committed to branch-2 now, I'll wait till FRI noon to see if there are objections for committing this to trunk as well.
was (Author: tucu00):
I'll be commit to branch-2 now. I'll wait till FRI noon to see if there are objections for committing this to trunk as well.
> Distributed cache conflicts breaks backwards compatability
> ----------------------------------------------------------
>
> Key: MAPREDUCE-4549
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4549
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.23.3, 2.0.2-alpha
> Reporter: Robert Joseph Evans
> Assignee: Robert Joseph Evans
> Priority: Critical
> Fix For: 2.0.3-alpha, 0.23.5
>
> Attachments: MAPREDUCE-4549-trunk.patch, MR-4549-branch-0.23.txt
>
>
> I recently put in MAPREDUCE-4503 which went a bit too far, and broke backwards compatibility with 1.0 in distribtued cache entries. instead of changing the behavior of the distributed cache to more closely match 1.0 behavior I want to just change the exception to a warning message informing the users that it will become an error in 2.0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira