Hi.
Sorry, if this was already discussed, I haven't found any trace in github
issues.
There is the following discrepancy in xcom_pull behavior between Airflow 2
and 3:
In case of the xcom_pull with task_ids=["{task_id}"] (list with one value):
- in Airflow 2 LazyXComSelectSequence is returned (with one object)
- in Airflow 3 the value itself is returned
Details in github issue:
https://github.com/apache/airflow/issues/49540
Similar/related issue https://github.com/apache/airflow/issues/46513.
Since it is a change in the public XCOM interface, it is quite likely that
it will break many DAGs.
We should fix it in Airflow 3 or describe it in the migration guide (if it
is intended change).
Is it an intended change, or a miss?
--
Eugene
