Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

Oozie - Fork, join, subflow - No Fork for Join [join-fork-actions] to pair with

avatar
Rising Star

Hi,

I have an Oozie workflow, with forks and join. I ma getting below error on execution-

No Fork for Join [join-fork-actions] to pair with.

here is the way workflow looks like -

<join name="join-fork-actions" to="end" />
<fork name="fork-actions">
<path start="InsertClaimInfo" />
<path start="InsertPartiesInvolved" /> <path start="InsertPaymentInfo" />
<path start="InsertPolicyInfo" />
</fork>
<action name="InsertClaimInfo">
<sub-workflow>
<app-path>${SUB_APP_PATH}Sub_WF_RESERVE_FEATURE_Insert_claiminfo.xml</app-path>
<propagate-configuration/> </sub-workflow>
<ok to="join-fork-actions"/>
<error to="fail" /> </action>
similar subflows for other actions in fork.
Subflows are defined like this -
<action name="insert_run_date">
<hive xmlns="uri:oozie:hive-action:0.2">
<job-tracker>${jobTracker}</job-tracker>
<name-node>${nameNode}</name-node>
<job-xml>${hive_conf_path}</job-xml>
<configuration> <property> <name>mapred.job.queue.name</name> <value>${queueName}</value> </property> <property> <name>tez.lib.uris</name> <value>${tez_lib_path}</value> </property> <property> <name>oozie.launcher.mapred.job.queue.name</name> <value>${queueName}</value> </property> </configuration> <script>${Reserve_Feature_Insert_claiminfo}</script> <param>SCHEMA_NAME=${DATABASE_NAME}</param> <param>run_date_path=${run_var_path_insert}</param> <param>Qname=${queueName}</param> </hive>
<ok to="get_run_date" />
<error to="fail" />
</action>

Any solution???

Error: No Fork for Join [join-fork-actions] to pair with.

1 ACCEPTED SOLUTION

avatar
Super Collaborator

Replace

<ok to="get_run_date" />

With

<ok to="join-fork-actions" />

In general each of the "subflows" should end up with the join node.

View solution in original post

1 REPLY 1

avatar
Super Collaborator

Replace

<ok to="get_run_date" />

With

<ok to="join-fork-actions" />

In general each of the "subflows" should end up with the join node.