[ 
https://issues.apache.org/jira/browse/OOZIE-1403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678644#comment-13678644
 ] 

Kevin Olson commented on OOZIE-1403:
------------------------------------

Hi Robert,

I'll need to sanitize the workflows and probably won't be able to do that till 
sometime next week. That being said, I do indeed have forks/joins within the 
workflow.  However they are logically separated in the DAG from the scenarios 
that I listed as having problems with.

This is the full exception I'm getting (not very useful I'm afraid, as I 
couldn't find a corresponding stacktrace in the logs): 

OozieClientException: org.apache.oozie.DagEngineException: E0743: Multiple "ok 
to" transitions to the same node, [oldDatasetDelete], are not allowed
                
> 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

Reply via email to