[GitHub] [airflow] dimberman opened a new issue #7928: Documentation says Sub-DAG names follow a convention, but in reality it's enforced

[GitBox <gi...@apache.org>]

dimberman opened a new issue #7928: Documentation says Sub-DAG names follow a convention, but in reality it's enforced
URL: https://github.com/apache/airflow/issues/7928
 
 
   
   
   **Apache Airflow version**:
   
   
   **Kubernetes version (if you are using kubernetes)** (use `kubectl version`):
   
   **Environment**:
   
   - **Cloud provider or hardware configuration**:
   - **OS** (e.g. from /etc/os-release):
   - **Kernel** (e.g. `uname -a`):
   - **Install tools**:
   - **Others**:
   **What happened**:
   
   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.
   
   **What you expected to happen**:
   
   
   **How to reproduce it**:
   
   
   **Anything else we need to know**:
   
   Moved here from https://issues.apache.org/jira/browse/AIRFLOW-332
       

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services