GitHub user potiuk added a comment to the discussion: Allow tasks downstream of `setup` tasks to have `trigger_rule` other than `ALL_SUCCESS`
Same issue as #48451 -> converting to a discussion. Setup and teardown are designed in the way that they MUST succed. If you want to do conditional behaviour of those, you have to implement "ifs" in your taskflow code that is used for setup/teardown and avoid doing any job, but still succeed. This is far simpler and straightforward and follows the - clearly documented semantics of setup/teardown tasks. The setup tasks mus be "green" (no matter what they do or don't do) in order to exacute whatever depends on setup. This is the basic assumption here. GitHub link: https://github.com/apache/airflow/discussions/48992#discussioncomment-12774215 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
