I believe so. Even we have seen this behaviour. Our users usually have the <coordinator-app> timezone in UTC and only <dataset> in different timezones.
Regards, Rohini On Tue, Mar 4, 2014 at 5:12 PM, bowen zhang <[email protected]> wrote: > Hi guys, > I have a coordinator job frequency DST transition question. If I schedule > a job to run at 8am everyday with frequency=1440 minutes and > timezone="America/Los Angeles", then the job will start running at 9am > after March 9th, 2014. > If you look at the line > "start.add(freqTU.getCalendarUnit(), lastActionNumber * > Integer.parseInt(coordJob.getFrequency()));" in > CoordMaterializeTransitionXCommand in materializeActions() function, this > line doesn't seem to take care of the DST transition. Is this the desired > behavior for oozie? > Bowen >
