No it would not. a day follows DST rules, a minute does not. thx
On Fri, Mar 11, 2016 at 1:04 PM, Alvin Chyan <[email protected]> wrote: > As a follow up question, is this auto-handling of daylight savings only if > we use "${coord:days(1)}"? Would frequency="${coord:minutes(160)}" also > work? > > Thanks! > > > *Alvin Chyan*Sr. Software Engineer, Data > 901 Marshall St, Suite 200, Redwood City, CA 94063 > > > turn.com <http://www.turn.com/> | @TurnPlatform > <https://twitter.com/@TurnPlatform> > > This message is Turn Confidential, except for information included that is > already available to the public. If this message was sent to you > accidentally, please delete it. > > On Fri, Mar 11, 2016 at 12:31 AM, Morgrim Murdargent < > [email protected]> wrote: > > > Hello Jagat. > > > > Thanks for this answer. > > > > I already readed the documentation but I didn't understand it ;-).. > > > > But indeed, if I read the paragraphe 7.2. Handling Timezones with > Daylight > > Saving Time, for the first use-case, the one that interests me because > the > > coordinator is daily, it is written the following information : > > ### > > Because the ${coord:days(1)} EL function is used to specify the job > > frequency, each coordinator action will be materialized (created) at > 00:00 > > EST5EDT regardless of timezone daylight-saving adjustments (05:00 UTC in > > Winter and 04:00 UTC in Summer) > > ### > > > > So, the coordinator action will be created at : > > - 05:00 UTC in Winter time (DST disabled) > > - 04:00 UTC in Summer Time (DST enabled). > > > > UTC = GMT. > > > > In Winter Time, France is in GMT+1 > > In Summer Time, France is in GMT+2 > > > > It means that : > > - 05:00 UTC means 06:00 GMT+1 in France in Winter Time > > - 04:00 UTC means 06:00 GMT+2 in France in Summer Time > > > > So normally, if I understood well, I shoudln't have any visible > > modification of the hour launch, no ? > > It seems native in Oozie ? > > > > Thank you in advance for your help. > > > > Best regards. > > > > Morgrim > > > > On Thu, Mar 10, 2016 at 8:36 AM, Jagat Singh <[email protected]> > wrote: > > > > > Hi, > > > > > > Did you see > > > > > > > > > > > > https://oozie.apache.org/docs/4.2.0/CoordinatorFunctionalSpec.html#a7._Handling_Timezones_and_Daylight_Saving_Time > > > > > > Thanks, > > > > > > Jagat Singh > > > > > > On Wed, Mar 9, 2016 at 10:13 PM, Morgrim Murdargent < > > > [email protected] > > > > wrote: > > > > > > > Hello ! > > > > > > > > We will soon have the activation of the daylight saving time here. > (at > > > the > > > > end of March) > > > > > > > > It means that France will switch its timezone from GMT+1 to GMT+2. > > > > > > > > In October, when we had the deactivation of DST, we switched from > GMT+2 > > > to > > > > GTM+1. We noticed that all the coordinators were launching at the > wrong > > > > hour. > > > > > > > > Example : a coordinator usually launching once a day at 3 pm when DST > > is > > > > enabled, was launching jobs at 2 pm when DST was disabled. > > > > > > > > So we think we will encounter this problem again at the end of March > > when > > > > DST will be activated but in the other direction. > > > > > > > > Some of our coordinators are launching once a day. We want them to > > always > > > > launch at the system hour. I mean, if a coordinator launches once a > day > > > at > > > > 3 pm during winter time (GMT+1), I want it to launch at 3 pm during > > > summer > > > > time (GMT+2). > > > > > > > > Is it possible ? > > > > > > > > I read the documentation in Oozie to handle the DST, but it did not > > > answer > > > > to my use case (or maybe I didn't understand ^_^). > > > > > > > > BR. > > > > > > > > Morgrim. > > > > > > > > > >
