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 2013/06/06 23:38:20 UTC

[jira] [Updated] (OOZIE-1403) forkjoin validation blocks some valid cases involving decision nodes

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

Robert Kanter updated OOZIE-1403:
---------------------------------

    Description: 
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}

  was:
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 go to A>
   <else go to B>
</decision>
<action A>
   <ok to C>
</action A>
<action B>
   <ok to C>
</action B>
{noformat}

    
> 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