[jira] [Created] (AIRFLOW-332) Documentation says Sub-DAG names follow a convention, but in reality it's enforced

["Jon McKenzie (JIRA)" <ji...@apache.org>]

Jon McKenzie created AIRFLOW-332:
------------------------------------

             Summary: Documentation says Sub-DAG names follow a convention, but in reality it's enforced
                 Key: AIRFLOW-332
                 URL: https://issues.apache.org/jira/browse/AIRFLOW-332
             Project: Apache Airflow
          Issue Type: Bug
          Components: operators
            Reporter: Jon McKenzie
            Priority: Minor


Currently, the documentation states that a Sub-DAG's name should follow the convention {{<parent_dag_id>.<sub_dag_id>}}. In reality, this is not just a convention, but it is enforced, and a {{SubDagOperator}} will fail to load if its name is incorrect. The documentation should be updated to be a little clearer in this regard.

Ideally, it would also be nice to either specify via an option that this validation should take place (or not), or be easier to subclass {{SubDagOperator}} and override the validation, so that users can have their own naming conventions.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)