[
https://issues.apache.org/jira/browse/OOZIE-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13504444#comment-13504444
]
Mohammad Kamrul Islam commented on OOZIE-1089:
----------------------------------------------
Is there anyway for oozie to enforce the uniqueness of jar in DC? Currently if
same jar file is included in multiple places (such as wf/lib. user/lib,
share/lib), there is no issue. With this new hadoop DC behavior, it will be an
issue. That will break Oozie backward compatibility.
>From the above perspective, can you please comment on the proposed two options
>that I mentioned above?
> 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, OOZIE-1089-trunk.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
