oozie coordinator job frequency DST transition

[bowen zhang <bo...@yahoo.com>]

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

Re: oozie coordinator job frequency DST transition

[Shwetha GS <sh...@inmobi.com>]

Calendar.add() takes care of DST transition


On Thu, Mar 6, 2014 at 4:04 AM, bowen zhang <bo...@yahoo.com> wrote:

> Isn't it ideal that the job is still running at 8am after March 9th? Oozie
> doc says oozie handles DST transition for timezones. I don't see here how
> oozie is really handling any DST transition.
> Bowen
>
>
>
>
>
> On Wednesday, March 5, 2014 12:04 PM, Rohini Palaniswamy <
> rohini.aditya@gmail.com> wrote:
>
> 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 <bo...@yahoo.com>
> 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
> >
>

-- 
_____________________________________________________________
The information contained in this communication is intended solely for the 
use of the individual or entity to whom it is addressed and others 
authorized to receive it. It may contain confidential or legally privileged 
information. If you are not the intended recipient you are hereby notified 
that any disclosure, copying, distribution or taking any action in reliance 
on the contents of this information is strictly prohibited and may be 
unlawful. If you have received this communication in error, please notify 
us immediately by responding to this email and then delete it from your 
system. The firm is neither liable for the proper and complete transmission 
of the information contained in this communication nor for any delay in its 
receipt.

Re: oozie coordinator job frequency DST transition

[bowen zhang <bo...@yahoo.com>]

Isn't it ideal that the job is still running at 8am after March 9th? Oozie doc says oozie handles DST transition for timezones. I don't see here how oozie is really handling any DST transition.
Bowen





On Wednesday, March 5, 2014 12:04 PM, Rohini Palaniswamy <ro...@gmail.com> wrote:
 
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 <bo...@yahoo.com> 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
>

Re: oozie coordinator job frequency DST transition

[Rohini Palaniswamy <ro...@gmail.com>]

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 <bo...@yahoo.com> 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
>