Hi John, There are couple of ways, i can think of: 1. Why don't you create a file in your WF action, in place of submitting a coord? Submit your coord separately and give the file (that is created by WF action) as data dependent. In this case, coord will not do anything until the WF action creates the file.
2. You can write a WF action that will emulate the coord submission. WF Action can utilize XOozieClient java class. I didn't think a lot on this approach though. If you are note using Oozie with security, it should be fine. If you prefer this option and have more detail question, please let us know. Regards, Mohammad ----- Original Message ----- From: John Armstrong <[email protected]> To: "[email protected]" <[email protected]> Cc: Sent: Monday, August 20, 2012 1:04 PM Subject: Submitting a coordinator from a workflow Hi, everybody. I was wondering if there's a good way to submit a coordinator job as a workflow action. A little more explicitly: I'm setting up some machine learning models and using Oozie coordinators to handle periodic future updates. But before I do that, I use an Oozie workflow to train my model up to the present and then do some post-processing. I'd like to use that workflow to schedule the coordinator once the model is trained. Some pseudo-descriptors: initialization train-model-to-present => post-process-past-models daily updates update-model-for-today => post-process-updated-model coordinator each day => submit daily-update workflow I'd like initialization to have a fork after train-model-to-present; one branch is the post-process-past-models sub-workflow like now, but the other one submits the coordinator to Oozie so I don't have to do it separately. Any thoughts? TIA
