Hi, Quoting from the Oozie Coordinator Docs:
"Oozie processes coordinator jobs in a fixed timezone with no DST (typically UTC ), this timezone is referred as 'Oozie processing timezone'." https://oozie.apache.org/docs/4.2.0/CoordinatorFunctionalSpec.html#a4._Datetime_Frequency_and_Time-Period_Representation Thanks, Abhishek On Mon, Apr 4, 2016 at 4:20 PM, Morgrim Murdargent <[email protected]> wrote: > Hello ! > > Any possible help from oozie developpers ? > > Best regards. > > Morgrim. > > On Wed, Mar 30, 2016 at 5:05 PM, Morgrim Murdargent < > [email protected] > > wrote: > > > Hello everyone ! > > > > I send you this mail because I have a problem with a coordinator with a > > cron syntax frequency and the daily saving time. > > > > The frequency is set to the following : > > > > 0-59/30 6-18 * * * > > > > I read that when we use the cron syntax, the timezone used is the one of > > the Oozie Server, which means by default UTC. And it is impacted when > there > > is the DST activation/deactivation. > > > > My question is the following : is it possible, with the cron syntax, to > > take into account the timezone set in the coordinator xml file, in order > to > > handle properly the DST, just like we use the ${coord:days(1)} ? > > > > I want this job to always launch from 6 am local time to 8 pm local time > > every 30 minuts, and I don't want to modify it each time we > enable/disable > > DST. > > > > Best regards. > > > > Morgrim. > > > > >
