Try this. It will work fine in UTC but if you are using different timezone.
You need to use tzoffset function, more detail @
http://oozie.apache.org/docs/4.0.0/CoordinatorFunctionalSpec.html#a6.6.5._coord:tzOffset_EL_Function_for_Synchronous_Datasets
<coordinator-app name="coord" frequency="${coord:days(1)}"
start="2010-05-01T20:00Z" end="${coordEndTime}" timezone="UTC"
xmlns="uri:oozie:coordinator:0.4">
<datasets>
<dataset name="a" frequency="${coord:hours(1)}"
initial-instance="2010-05-01T20:00Z" timezone="UTC">
<uri-template>${nameNode}/${YEAR}/${MONTH}/${DAY}/${HOUR}</uri-template>
<done-flag></done-flag>
</dataset>
<input-events>
<data-in name="input" dataset="a">
<start-instance>${coord:current(-23)}</start-instance>
<end-instance>${coord:current(0)}</end-instance>
</data-in>
</input-events>
From: Serega Sheypak <[email protected]>
To: [email protected]
Sent: Friday, May 8, 2015 4:33 AM
Subject: Set input-event instances
Hi, I have a coordinator. It wakes up each day and consumes hourly-based
paths.
The problem is that I coordinator should consume these paths:
/my/path/2015/05/20
/my/path/2015/05/21
/my/path/2015/05/22
...
/my/path/2015/06/04
How can I specify these instances using
<start-instance />
<end-instance />
