Harsh, Yes, sub-workflow should be the right solution for me. Thanks!
Yongcheng -----Original Message----- From: Harsh J [mailto:[email protected]] Sent: Tuesday, November 20, 2012 7:47 AM To: [email protected] Subject: Re: Multiple Actions for Coordinator App Hey Yongcheng, Do sub-workflow actions not solve your need? A coordinator isn't a set of workflow apps but a coordinated execution of one. If you want a DAG of separated workflows, then you could write a workflow of sub-workflows. Docs for sub-workflow are at http://oozie.apache.org/docs/3.2.0-incubating/WorkflowFunctionalSpec.html#a3.2.6_Sub-workflow_Action. On Mon, Nov 19, 2012 at 11:38 PM, Yongcheng Li <[email protected]> wrote: > Hi, > > I have several independent workflow apps I need to run. They share many > properties and I feel that it makes sense to put them in just one coordinator > application. However, a coordinator application only allows one action which > only allows one workflow app in it. So I need to either combine the two > independent workflow applications into one or create two separate coordinator > apps. Does it make sense to allow multiple actions or workflow apps in one > coordinator app? If not, what is the best practice for this scenario? > > Thanks! > > Yongcheng -- Harsh J
