GitHub user pykenny edited a comment on the discussion: Dynamic mapped tasks group arguments are interpreted as MappedArgument when provided to classic operators
Within the decorated task group context, parameter set `(project, dataset, table_name, partition_id)` seems to be some native Python variables (strings as for the case proposed) that accepts the values unpacked from upstream XCom, but actually they are special objects that instruct tasks defined within the context what should be pulled from XCom (from which upstream task, and value corresponds to which key) and send to the (templated) parameters for running the task. Concatenating them through f-string without task context merely stringifies these objects together so that's why the weird outcome happened. GitHub link: https://github.com/apache/airflow/discussions/40728#discussioncomment-12100820 ---- This is an automatically sent email for commits@airflow.apache.org. To unsubscribe, please send an email to: commits-unsubscr...@airflow.apache.org
