You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Daniel Imberman (Jira)" <ji...@apache.org> on 2020/03/25 19:17:00 UTC
[jira] [Closed] (AIRFLOW-197) Import SubDagOperator not consistent
[ https://issues.apache.org/jira/browse/AIRFLOW-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Imberman closed AIRFLOW-197.
-----------------------------------
Resolution: Auto Closed
> Import SubDagOperator not consistent
> ------------------------------------
>
> Key: AIRFLOW-197
> URL: https://issues.apache.org/jira/browse/AIRFLOW-197
> Project: Apache Airflow
> Issue Type: Bug
> Components: operators
> Affects Versions: 1.6.2
> Environment: OS X
> Reporter: Pedro M Duarte
> Priority: Trivial
> Labels: beginner
>
> I observe conflicting behavior when doing
> a) `from airflow.operators import SubDagOperator`
> or
> b) `from airflow.operators.subdag_operator import SubDagOperator`
> In the first case all the subdags that I define via the `SubDagOperator` are correctly handled by airflow. For example
> ```
> $ airflow list_dags
> ...
> test_emailsubdag
> test_emailsubdag.email
> ...
> ```
> In the second case, the subdag's go unnoticed by airflow:
> ```
> $ airflow list_dags
> ...
> test_emailsubdag
> ...
> ```
> This issue is not a big deal, as I can always stick to option a). But after looking at the contents of `operators/__init__.py` I am having a hard time understanding the observed behavior.
> Would really appreciate it if someone could comment on this for clarification.
> Thanks!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)