You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Airflow documentation for Dynamic Task Mapping states that "mapped tasks are created based on the output of a previous task".
Nothing is said in docs and examples about how to create mapped task based on output of any upstream task. For example as shown
, plus_10_TF is created based on outputs of one_two_three_TF, but my logic requires intermediate task to sit between and does not require direct dependency between one_two_three_TF and plus_10_TF.
QUESTION
Does airflow 2.7 support mapped tasks based on output of specified upstream task (data flow) without implicitly creating dependency (control flow)?
If not, then why not to separate data flow and control flow in future releases?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello,
PROBLEM
Airflow documentation for Dynamic Task Mapping states that "mapped tasks are created based on the output of a previous task".
Nothing is said in docs and examples about how to create mapped task based on output of any upstream task. For example as shown
, plus_10_TF is created based on outputs of one_two_three_TF, but my logic requires intermediate task to sit between and does not require direct dependency between one_two_three_TF and plus_10_TF.
QUESTION
Beta Was this translation helpful? Give feedback.
All reactions