Antalares commented on issue #72386: URL: https://github.com/apache/airflow/issues/72386#issuecomment-5907123459
I agree with this point. Mark as Skipped should not bypass or override the DAG's existing dependency and trigger_rule semantics. The purpose of the feature is simply to let an operator say: "This pending task must not run for this particular DAG run." What happens downstream should remain entirely governed by the DAG definition. If the DAG is designed to tolerate a skipped task, the run can continue. If it requires ALL_SUCCESS, then the downstream task should remain blocked - which is the expected behavior. The important part for me is that we can record the operational decision as SKIPPED rather than incorrectly marking the task as SUCCESS. And I agree that this should only be allowed for Task Instances that have not started running yet. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
