Uploaded image for project: 'Oozie'
  1. Oozie
  2. OOZIE-3350

Forkjoin validation does not fail if a node is reachable from two different forks

Add voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 4.3.1
    • None
    • core
    • None

    Description

      when "multiple ok to same node" under decision node, forkjoin validation error.

       

      such as below example, 'action_C' and 'action_D' both transition to 'action_E'.

      But, because they are under same topDecisionParent 'decision_A', validator will not throw any exception. 

       

      <decision name = 'decision_A'>

          <case to = 'fork_B'></case>

          <case to = 'action_G'></case>

      </decision>

      <fork name = 'fork_B'>

          <path start = 'action_C'/>

          <path start = 'action_D'/>

      </fork>

      <action name = 'action_C'>

          <ok to = 'action_E'>

          <error to = 'kill'>

      </action>

      <action name = 'action_D'>

          <ok to = 'action_E'>

          <error to = 'kill'>

      </action>

      <action name = 'action_E'>

          <ok to = 'join_F'>

          <error to = 'kill'>

      </action>

      <join name = 'join_F'>

          <ok to = 'action_H'>

          <error to = 'kill'>

      </join>

      <action name = 'action_G'>

          <ok to = 'action_H'>

          <error to = 'kill'>

      </action>

      <action name = 'action_H'>

          <ok to = 'end'>

          <error to = 'kill'>

      </action>

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            Dr.hahaha wang jinyin

            Dates

              Created:
              Updated:

              Time Tracking

                Estimated:
                Original Estimate - 120h
                120h
                Remaining:
                Remaining Estimate - 120h
                120h
                Logged:
                Time Spent - Not Specified
                Not Specified

                Slack

                  Issue deployment