[OOZIE-1403] forkjoin validation blocks some valid cases involving decision nodes

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.3.2
• Fix Version/s: 4.1.0
• Assignee: Robert Kanter
• Reporter: Robert Kanter
• Created: 06/Jun/13 21:35
• Updated: 08/Nov/17 15:17
• Resolved: 07/Aug/13 21:58

Description

As described here 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:

<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>

2) This uses a decision node to "replace" an action based on foo:

<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>

Issue Links

• relates to: OOZIE-1443 forkjoin validation should not allow a fork to go to the same node multiple times
• relates to: OOZIE-1035 Improve forkjoin validation to allow same errorTo transitions