You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Robert Kanter (JIRA)" <ji...@apache.org> on 2012/11/05 18:56:13 UTC

[jira] [Updated] (OOZIE-1035) Improve forkjoin validation to allow same errorTo transitions

     [ https://issues.apache.org/jira/browse/OOZIE-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Kanter updated OOZIE-1035:
---------------------------------

    Attachment: OOZIE-1035.patch

I rewrote the forkjoin validation; it's much more lenient now.  It essentially just checks that every path from a fork eventually goes to an associated join.  I also updated the tests and added a new one.  
                
> 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
>
>         Attachments: 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 or end 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