airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bolke de Bruin (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AIRFLOW-1710) Add timezone setting to Airflow DAG
Date Mon, 27 Nov 2017 20:43:01 GMT

     [ https://issues.apache.org/jira/browse/AIRFLOW-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Bolke de Bruin resolved AIRFLOW-1710.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 1.10.0

Issue resolved by pull request #2781
[https://github.com/apache/incubator-airflow/pull/2781]

> Add timezone setting to Airflow DAG
> -----------------------------------
>
>                 Key: AIRFLOW-1710
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-1710
>             Project: Apache Airflow
>          Issue Type: Sub-task
>          Components: DAG
>    Affects Versions: 1.9.0
>            Reporter: Chris Riccomini
>            Assignee: Bolke de Bruin
>             Fix For: 1.10.0
>
>
> 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)

Mime
View raw message