[
https://issues.apache.org/jira/browse/OOZIE-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13504379#comment-13504379
]
Roman Shaposhnik commented on OOZIE-1089:
-----------------------------------------
A strong +1 -- this seems to be a non-invasive change that is easy to remove
once we no longer need the workaround, it doesn't change the default behavior
and it was tested on Hadoop 2.0.2, Hadoop 1.1.0 and Hadoop 1.0.X
Now if I only to make one more request this would be to RELNOTE this workaround
in the Oozie docs for the upcoming release.
> DistributedCache workaround for Hadoop 2.0.2-alpha
> --------------------------------------------------
>
> Key: OOZIE-1089
> URL: https://issues.apache.org/jira/browse/OOZIE-1089
> Project: Oozie
> Issue Type: Bug
> Components: workflow
> Affects Versions: 3.3.0
> Reporter: Alejandro Abdelnur
> Assignee: Alejandro Abdelnur
> Fix For: 3.3.0
>
> Attachments: OOZIE-1089.patch
>
>
> As explained in MAPREDUCE-4820, Hadoop 2.0.2-alpha introduced a duplicate
> check that exposes an change of behavior in how the distributed-cache works
> in Hadoop 2 (as opposed to Hadoop-1).
--
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
