[
https://issues.apache.org/jira/browse/AIRFLOW-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16202511#comment-16202511
]
Chris Riccomini commented on AIRFLOW-1710:
------------------------------------------
Another alternative that people are doing to hack around this issue:
https://stackoverflow.com/questions/43662571/how-to-properly-handle-daylight-savings-time-in-apache-airflow/43664910#43664910
> Add timezone setting to Airflow DAG
> -----------------------------------
>
> Key: AIRFLOW-1710
> URL: https://issues.apache.org/jira/browse/AIRFLOW-1710
> Project: Apache Airflow
> Issue Type: Bug
> Components: DAG
> Affects Versions: 1.9.0
> Reporter: Chris Riccomini
>
> We have some use cases where we'd like to run DAGs pegged to a specific
> timezone.
> Customers want things to happen in their time zone. If they have DST, it's
> not a constant offset from UTC. If they aren't in the US, their DST isn't a
> constant offset from California's DST (where we run). GB, for example.
> One way to solve this would be to have the DAG start with PythonOperator task
> that calculates the difference between UTC and the expected timezone, and
> sleeps for that amount of time.
> Another (cleaner?) way would be to add a field to the DAG model that allows
> the DAG author to specify the timezone that the DAG should be scheduled in.
> For example, we could have our Airflow box continue to run on UTC, but
> schedule a specific DAG for Pacific/US, which would adjust according to
> daylight savings time. We could schedule other DAGs to run on GB DST, etc.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
