kurtqq commented on pull request #8082: URL: https://github.com/apache/airflow/pull/8082#issuecomment-716212362
> > > REMOVED is not background noise, dynamic dags can get REMOVED intermittently My point was that if in a specific run there is a task which has removed state in this run it should be ignored like it doesn't exist. So if you have` A-> [B,C] -> D` and `B` is removed Airflow will consider this to be: `A -> C -> D` Otherwise you might get into a world of troubles. In this PR you try to address the dag state but there is also a very big issue of how trigger rules to be handled. If trigger rule is `ALL_SKIP `does it means REMOVED is OK for it or not? What about `all_success`? `all_failed `? I think it makes much more sense to go simple ---------------------------------------------------------------- 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]
