You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by "Ash Berlin-Taylor (JIRA)" <ji...@apache.org> on 2018/09/27 08:56:00 UTC

[jira] [Updated] (AIRFLOW-3123) Allow nested use of DAG as a context manager

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

Ash Berlin-Taylor updated AIRFLOW-3123:
---------------------------------------
    Summary: Allow nested use of  DAG as a context manager  (was: DAG context manager fails in nested cases)

> Allow nested use of  DAG as a context manager
> ---------------------------------------------
>
>                 Key: AIRFLOW-3123
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-3123
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: DAG
>            Reporter: Newton Le
>            Assignee: Newton Le
>            Priority: Major
>
> DAG context manager fails under some cases with nested contexts:
> {code:python}
> with DAG( ... ) as dag:
>   op1 = Operator()
>   with dag:
>     op2 = Operator()
>   op3 = Operator
> {code}
> op3 will not continue to be assigned the original DAG after exiting the nested context.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)