Dejace, It is simple, you just do the math (+7hrs) and use GMT for everything. The TZ attributes, if used, are for Oozie to do the correct DST adjustment (+/-1 hr for day or greater frequencies)
Thx On Wed, May 30, 2012 at 7:40 PM, dejace sr <[email protected]> wrote: > re-posting this as I didn't get any answer. > > On Wed, May 23, 2012 at 9:02 PM, dejace sr <[email protected]> wrote: > > > Hi, > > > > I have a coordinator job which runs once every day and looks for a single > > folder created by an application which runs in GMT-7 TZ. > > How do I specify the data set dependency in oozie? > > > > I am using oozie 2.3.0 > > > > -Thanks > > > > 1. Tried the below: > > > > oozie logs say: No Notification URL is defined > > > > STARTED Coordinator Notification > > actionId=0000611-120517003143041-oozie-oozi-C@1 : WAITING > > 2012-05-23 20:26:27,441 INFO CoordActionNotification:525 - USER[user1] > > GROUP[users] TOKEN[] APP[Test-App] > > JOB[0000611-120517003143041-oozie-oozi-C] ACTION[-] No Notification URL > is > > defined. Therefore nothing to notify for job > > 0000611-120517003143041-oozie-oozi-C action ID > > 0000611-120517003143041-oozie-oozi-C@1 > > > > > > > ------------------------------------------------------------------------------------------------ > > > > jobScheduleBeginDateTime=2011-04-18T20:00Z > > jobScheduleEndDateTime=2011-04-19T20:00Z > > jobRunFrequency=1440 > > jobScheduleTimeZone=UTC > > > > <coordinator-app name="Test-App" frequency="jobRunFrequency" > > start="${jobScheduleBeginDateTime}" end="${jobScheduleEndDateTime}" > > timezone="${jobScheduleTimeZone}" xmlns="uri:oozie:coordinator:0.1"> > > > > <datasets> > > <dataset name="input1" frequency="${jobRunFrequency}" > > initial-instance="${jobScheduleBeginDateTime}" > > timezone="${jobScheduleTimeZone}"> > > > > > <uri-template>${nameNode}/${hdfsRoot}/${YEAR}/${MONTH}/${DAY}/${HOUR}/00</uri-template> > > </dataset> > > </datasets> > > > > <input-events> > > <data-in name="coordInput1" dataset="input1"> > > <instance>${coord:current(-7)}</instance> > > </data-in> > > </input-events> > > : > > : > > > > > > > ------------------------------------------------------------------------------------------------ > > > > 2. Tried the below too: It kicked off the wf with out even checking for > > the presence of folder. > > > > <datasets> > > <dataset name="input1" frequency="${jobRunFrequency}" > > initial-instance="${jobScheduleBeginDateTime}" > > timezone="${jobScheduleTimeZone}"> > > > > > <uri-template>${nameNode}/${hdfsRoot}/${YEAR}/${MONTH}/${DAY}/${HOUR}/00</uri-template> > > </dataset> > > </datasets> > > > > <data-in name="coordInput1" dataset="input1"> > > <start-instance>${coord:current(-7)}</start-instance> > > <end-instance>${coord:current(-7)}</end-instance> > > </data-in> > > > > 3. same...kicks of wf with out chking for the folder > > > > <datasets> > > <dataset name="input1" frequency="${jobRunFrequency}" > > initial-instance="${jobScheduleBeginDateTime}" > > timezone="${jobScheduleTimeZone}"> > > > > > <uri-template>${nameNode}/${hdfsRoot}/${YEAR}/${MONTH}/${DAY}/${HOUR}/00</uri-template> > > </dataset> > > </datasets> > > > > > > 4. . -7 and 0 for st and end inst...chking and waiting > > > > <data-in name="coordInput1" dataset="input1"> > > <start-instance>${coord:current(-7)}</start-instance> > > <end-instance>${coord:current(0)}</end-instance> > > </data-in> > > > > --> as per logs its looking for the below instead of > > 2011/04/18/13/00/_SUCCESS > > > > In checkListOfPaths for: hdfs:// > qa.com:8020/root/2011/04/18/20/00/_SUCCESS > > > > > > > > > > > > > > >
