Or another possible way could be, in one workflow, use fork for subworkflow actions (one for W2, and the other for W3), then after join node, run subworkflow action for w1.
Ryota On 1/31/14 10:33 AM, "Mona Chitnis" <[email protected]> wrote: >Hi, > >Currently our Oozie model triggers coordinator workflows based on >availability of datasets, rather than workflow W1 triggering W2 directly. >You can accomplish it by having W2 mark W1¹s output dir as its dependency. > >Does that make sense? > >‹Mona > >On 1/31/14, 4:13 AM, "ZORAIDA HIDALGO SANCHEZ" <[email protected]> wrote: > >>Hi all, >> >>we have a set of workflows with dependencies among them. For instance, we >>have a W1 that can only run when W2 and W3 have been finished (and >>obviously the status is SUCCEEDED). >>I know that the Oozie coordinator can do calls to an HTTP url but this >>does not work for multiples dependencies. Is there any feature to >>accomplish this? >> >>Thanks in advance. >> >>________________________________ >> >>Este mensaje se dirige exclusivamente a su destinatario. Puede consultar >>nuestra política de envío y recepción de correo electrónico en el enlace >>situado más abajo. >>This message is intended exclusively for its addressee. We only send and >>receive email on the basis of the terms set out at: >>http://www.tid.es/ES/PAGINAS/disclaimer.aspx >
