[
https://issues.apache.org/jira/browse/OOZIE-1403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13681849#comment-13681849
]
Mona Chitnis commented on OOZIE-1403:
-------------------------------------
I agree. Its a valid case. Thinking about it, if the other fork - "TouchPar2"
went to "TouchDecEnd" before going to join, would that be valid currently?
Just being inside a decision block is giving false negative for otherwise valid
dag.
> 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 where the decision nodes are inside the forkjoin;
> when they are outside, its not a problem.
> 1) This uses a decision node to "insert" an action based on {{foo}}:
> {noformat}
> <fork>
> <goto decision>
> <goto join>
> </fork>
> <decision>
> <if foo, goto A>
> <else, goto B>
> </decision>
> <action A>
> <ok to="B">
> </action A>
> <action B>
> <ok to="join">
> </action B>
> <join>
> {noformat}
> 2) This uses a decision node to "replace" an action based on {{foo}}:
> {noformat}
> <fork>
> <goto decision>
> <goto join>
> </fork>
> <decision>
> <if foo, goto A>
> <else, goto B>
> </decision>
> <action A>
> <ok to="join">
> </action A>
> <action B>
> <ok to="join">
> </action B>
> <join>
> {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
