[
https://issues.apache.org/jira/browse/OOZIE-1403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13677731#comment-13677731
]
Robert Kanter commented on OOZIE-1403:
--------------------------------------
[~keolson], are you sure that those two scenario's don't work for you? I tried
creating two simple workflows, one for each of the structures above, and they
both worked fine. In fact, looking at the code, it won't do any of the
forkjoin checking if there are no forks in the workflow; can you paste the full
workflow which is throwing the exception? I'm thinking that there must be
something more complicated happening. Could you also paste the full exception
you're getting?
> forkjoin validation blocks some valid cases involving decision nodes
> --------------------------------------------------------------------
>
> Key: OOZIE-1403
> URL: https://issues.apache.org/jira/browse/OOZIE-1403
> Project: Oozie
> Issue Type: Bug
> Affects Versions: 3.3.2
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Fix For: trunk
>
>
> As described
> [here|https://issues.apache.org/jira/browse/OOZIE-1035?focusedCommentId=13676534&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13676534]
> in OOZIE-1035, the new forkjoin checker code is blocking some valid cases
> involving decision nodes.
> 1) This uses a decision node to "insert" an action based on {{foo}}:
> {noformat}
> <decision>
> <if foo, goto action A>
> <else, goto action B>
> </decision>
> <action A>
> <ok to="B">
> </action A>
> <action B>
> </action B>
> {noformat}
> 2) This uses a decision node to "replace" an action based on {{foo}}:
> {noformat}
> <decision>
> <if foo, goto A>
> <else, goto B>
> </decision>
> <action A>
> <ok to C>
> </action A>
> <action B>
> <ok to C>
> </action B>
> {noformat}
--
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
