Sign up to take part
Registered users can ask their own questions, contribute to discussions, and be part of the Community!
Registered users can ask their own questions, contribute to discussions, and be part of the Community!
Hi ,
I notice in our dataiku setup that triggers have to be defined in UTC.
So wanted to check if anyone knew how Daylight savings is handled for timebased triggers in this situation.
Spoiler alert!
We also think it's annoying to always rely on the server timezone for triggers, so we have been working hard to improve the situation... and this particular feature will be part of the upcoming DSS 9.0 release 🎉 .
As a bonus, here is what it will look like in DSS 9.0
 
 
I'm not sure. I'd imagine that the system uses UTC/GMT all the way through. As these do not have the idea of a Daylight savings shift. Then it is my guess that as local time changes relative to UTC/GMT that you will see a shift by the change for your Daylight Savings to Standard Shift.
Can you say anything more about what you have seen happen in your case, Or what you would like to have happened?
Hi NN,
Generally speaking, DSS will use the timezone of the server, which is usually UTC for most Linux servers like Tom mentioned. Unfortunately, it is currently not possible to specify a timezone or local timezone to be used when setting a time-based trigger for scenarios. However, this is an existing enhancement request that is already in our backlog but I will go ahead and append your use case for further review by our Product team.
Thanks,
Andrew
Spoiler alert!
We also think it's annoying to always rely on the server timezone for triggers, so we have been working hard to improve the situation... and this particular feature will be part of the upcoming DSS 9.0 release 🎉 .
As a bonus, here is what it will look like in DSS 9.0