[
https://issues.apache.org/jira/browse/OOZIE-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13676534#comment-13676534
]
Kevin Olson commented on OOZIE-1035:
------------------------------------
We recently upgraded to Oozie 3.3.2 and noticed what I believe (and hope!) is
an unintended consequence of this enhancement. Prior to 3.3.2 you could have a
decision that effectively added an additional action node into the DAG if a
certain condition was met, ie:
<decision>
<if foo, goto action A>
<else, goto action B>
</decision>
<action A>
<ok to="B">
</action A>
<action B>
</action B>
or similarly:
<decision>
<if foo go to A>
<else go to B>
</decision>
<action A>
<ok to C>
</action A>
<action B>
<ok to C>
</action B>
These DAG options were very helpful. Both of these use cases now throw errors
in 3.3.2. Was outlawing these intended, or accidental?
> Improve forkjoin validation to allow same errorTo transitions
> -------------------------------------------------------------
>
> Key: OOZIE-1035
> URL: https://issues.apache.org/jira/browse/OOZIE-1035
> Project: Oozie
> Issue Type: Improvement
> Components: workflow
> Affects Versions: trunk
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Priority: Minor
> Fix For: trunk, 3.3.2
>
> Attachments: OOZIE-1035.patch, OOZIE-1035.patch
>
>
> It seems common that users will have the "error to" transition from every
> action go to the same action node (e.g. email action), which then goes to the
> kill node instead of just going to the kill node directly. When this is done
> in action nodes within a forkjoin path, the forkjoin validation doesn't allow
> it. We should improve the forkjoin validation code to allow the same "error
> to" transition, as long as it eventually leads to a kill node.
--
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
