This can be achieved slightly indirectly. You can set your <dataset> <uri-template> to point to your input files’ parent directory, and set an arbitrary frequency to execute the coordinator. Set a timeout for the coordinator action, so it will timeout after a finite interval when no input file is present. Use some custom logic with a Java action in workflow, to look for ‘next unprocessed’ input file, since I’m guessing your input files do not follow a synchronous filename pattern.
On 5/21/14, 7:11 AM, "Raja.Aravapalli" <[email protected]<mailto:[email protected]>> wrote: Hi Can anyone guide me that, is it possible to control the coordinator application such way that, rather than triggering the workflow based on frequency(time based) to trigger the workflow certain specified no.of times. Let me elaborate what I need: Suppose I have four input files which I need to process in my input directory... Now, I want my coordinator to trigger the workflow on my input only 4times, as every time it triggers it process one file from my input directory. So, by default coordinator triggers the workflow based on time frequency we provide to it... but I want my coordinator to trigger based on no.of my input files rather than the frequency. Does it possible to configure in oozie coordinator.xml file. Any one please help me...... Regards, Raja.
