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

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

Nope, it's outside the forkjoin.  Here's a snippet:

<workflow-app name="sqoop-import-clients" xmlns="uri:oozie:workflow:0.1">
    <start to="prepSqoopImport"/>
    <action name="prepSqoopImport">
        <fs>
            <delete path="${sqoopImportFullOutput}"/>
            <delete path="${sqoopImportDeltaOutput}"/>
            <delete path="${mergedTablesIndexedOutput}"/>
            <delete path="${sqoopImportLastIdOutput}"/>
        </fs>
        <ok to="deltaOrFullDecision"/>
        <error to="fail"/>
    </action>
    <decision name='deltaOrFullDecision'>
        <switch>
            <case 
to="forking_0">${!fs:exists(concat(sqoopImportLastIdInput,'/part-r-00000.snappy'))}</case>
            <case to="forking_0">${!enableDeltas}</case>
            <case to="getLastDeltaValue">${enableDeltas}</case>
            <default to="forking_0"/>
        </switch>
    </decision>
    <action name='getLastDeltaValue'>
        <shell xmlns="uri:oozie:shell-action:0.1">
            <job-tracker>${jobTracker}</job-tracker>
            <name-node>${nameNode}</name-node>
            <configuration>
                <property>
                    <name>mapred.job.queue.name</name>
                    <value>default</value>
                </property>
            </configuration>
            <exec>shell.sh</exec>
            <argument>${sqoopImportLastIdInput}/part*</argument>
            
<file>${nameNode}/oozie/${env}/workflows/slurp/importTableClients/shell.sh#shell.sh</file>
            <capture-output/>
        </shell>
        <ok to="forking_0" />
        <error to="forking_0" />
    </action>

    <fork name="forking_0">

Throws a E0743
                
> 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 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}}:
> {noformat}
> <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>
> {noformat}
> 2) This uses a decision node to "replace" an action based on {{foo}}:
> {noformat}
> <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>
> {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