[
https://issues.apache.org/jira/browse/OOZIE-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505096#comment-13505096
]
Roman Shaposhnik commented on OOZIE-1089:
-----------------------------------------
[~rohini] The policy we have in Bigtop is to test RCs with stable components.
We don't test RC-to-RC or trunk-to-trunk since it presents too much of a moving
target. Hadoop 2.0.2 was released in mid. October -- that's when we switched.
So it tooks us a couple more weeks to start testing Oozie's RC and a week more
or so to file an issue. Given a 100% volunteer nature of Bigtop this strikes me
as rather expedient scale of testing (yes I'd love to have Oozie developers
monitoring my Oozie test runs in Bigtop so that issues could be identified
sooner).
It would be very nice if somebody can volunteer testing trunk-to-trunk or
RC-to-RC -- Bigtop has all the mechanisms in place, but we need eyeballs.
> 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
