[
https://issues.apache.org/jira/browse/OOZIE-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13504910#comment-13504910
]
Mohammad Kamrul Islam commented on OOZIE-1089:
----------------------------------------------
This was the root cause and that's why we asked hadoop team to retract the
patch from 0.23.
End user can't enforce the file name at the share/lib. We need to find a
resolution at Oozie level too. which one of the two options (mentioned above)
will be good for this? (btw, we could fix it in Oozie in later release)
About the patch:
My concern was to support hadoop 2.x for 3.3. The reasons are : Oozie was not
tested against 2.x. I heard pig streaming will not also work for some unrelated
issue. Moreover, not sure how stable is hadoop 2.x alpha.
Having said that, if it is must from your side, I'm good to go. +1.
One coding clarification comment :
The following line of code is only for writing a log in Launcher Main. right?
launcherConf.setBoolean("oozie.hadoop-2.0.2-alpha.workaround.for.distributed.cache",
true);
> 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
