Thanks for your response Max. As he correctly pointed out, you can configure timeout so that your coordinator waits and materializes an action finally when input dependencies are satisfied.
-- Mona Chitnis Oozie dev Yahoo! On 6/20/12 10:44 AM, "Maxime Petazzoni" <[email protected]> wrote: >Hi Etienne, > >* Etienne Dumoulin <[email protected]> [2012-06-20 12:37:24]: > >> I am looking at the coordinator documentation: >> >>http://incubator.apache.org/oozie/docs/3.1.3/docs/CoordinatorFunctionalSp >>ec.html >> >> I would like to build a complex workflow, from a daily update. >> >> Maybe I miss something, but I did not find what's happened if I do not >>have >> the daily file. >> >> What I am looking for is, let say there is an incident, the workflow >>does >> not get the daily file, >> but get two files the day after. Will it throw an error (sending a >>mail)? >> Will it be smart enough to launch two jobs the day after? > >If I remember and understand correctly, you can set a timeout (in the >controls section) to get the appropriate behavior. The timeout is the >amount of time, in minutes, that Oozie will wait for the input >conditions (here, the presence of your data files) to be satisfied. > >A value of 0 means no timeout, i.e. your coordinator materialization >will fail immediately if the file is not present. -1 means wait forever. >Any other ℕ+ value is a timeout in minutes. > >Finally, note that Oozie never sends emails on its own, and is only as >smart as you make it be :) > >/Max >-- >{ name: 'Maxime Petazzoni', title: 'Sr. Platform Engineer', > company: { name: 'Turn, Inc', url: 'http://www.turn.com' } }
