[
https://issues.apache.org/jira/browse/AIRFLOW-4933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Postelnik updated AIRFLOW-4933:
---------------------------------------
Description:
I have multiple dags defined in one file (understand this is not recommended).
I shared the same default_args between two dags and found that the latter dag
was running on UTC instead of the timezone of the start_date. Debugging, I
found the following line convert the start_date to UTC in the DAG init. A
deepcopy in the init should resolve this and allow a reusable set of defaults.
[https://github.com/apache/airflow/blob/master/airflow/models/dag.py#L255-L257]
was:
I have multiple dags defined in one file (understand this is not recommended).
I shared the same default_args between two dags and found that the latter dag
was running on UTC instead of the timezone of the start_date. Debugging, I
found the following line convert the start_date to UTC in the DAG init and it
must be doing it in-place. A deepcopy in the init should resolve this and allow
a reusable set of defaults.
[https://github.com/apache/airflow/blob/master/airflow/models/dag.py#L250]
> DAG init causes side effects on default args
> --------------------------------------------
>
> Key: AIRFLOW-4933
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4933
> Project: Apache Airflow
> Issue Type: Bug
> Components: DAG
> Affects Versions: 1.10.3
> Reporter: Richard Postelnik
> Priority: Trivial
>
> I have multiple dags defined in one file (understand this is not
> recommended). I shared the same default_args between two dags and found that
> the latter dag was running on UTC instead of the timezone of the start_date.
> Debugging, I found the following line convert the start_date to UTC in the
> DAG init. A deepcopy in the init should resolve this and allow a reusable set
> of defaults.
>
> [https://github.com/apache/airflow/blob/master/airflow/models/dag.py#L255-L257]
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
