[
https://issues.apache.org/jira/browse/MAPREDUCE-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13436076#comment-13436076
]
Alejandro Abdelnur commented on MAPREDUCE-4549:
-----------------------------------------------
Where was this discussed with the Oozie people? I'm not aware of this, I did
not see any discussion in the oozie-dev@ alias.
Would you please summarize the issue, how it affects Oozie and what is exactly
the impact of leaving it incompatible in Hadoop 2?
At first look I think we should keep backwards compatibility in Hadoop 2.
> 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
> Reporter: Robert Joseph Evans
> Assignee: Robert Joseph Evans
> Priority: Critical
> Attachments: 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
