RosterIn edited a comment on issue #4291: [AIRFLOW-1488] Add the 
TriggeredDagRunSensor operator
URL: https://github.com/apache/airflow/pull/4291#issuecomment-508651783
 
 
   @ashb for my use case I run DAG A.  task DAG_A_TASK_4 can't can't start if 
DAG_B is active.
   DAG_B can run up to 6 times simuontaniusly (max_active_dags=6) . 
   So what I care about is that in DAG_A I'll have sensor poking DAG_B for it's 
status. I can't specify run_id nor execution_date. I'm not poking specific run 
I'm poking the whole DAGs status.. all of them.. from 1 to 6 - together. So for 
this use case I need sensor that takes dag_id and dag_status and continue 
down_stream if the status is met. So you can't do that with ExternalTaskSensor  
which is why this PR is needed.
   
   I do think though that the semantic needs work in order not to confuse 
users. 
   It's confusing having ExternalTaskSensor  which can also poke dag run 
(https://github.com/apache/airflow/pull/4058 )
   
   **My suggestion**:
   
   **ExternalTaskSensor**   should poke only tasks.
   **TriggeredDagRunSensor** should be renamed to **ExternalDAGSensor**   with 
two functionalities
   1. the functionality of https://github.com/apache/airflow/pull/4058  (poking 
whole specific dag RUN)
   2. The functionality  of this PR (poking DAGs regardless of specific RUN e.g 
poking DAGs STATE)

----------------------------------------------------------------
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:
[email protected]


With regards,
Apache Git Services

Reply via email to