tirkarthi commented on issue #49737: URL: https://github.com/apache/airflow/issues/49737#issuecomment-2828637411
When the xcom values map 1:1 in length then the `map_index` of the downstream task can directly get the xcom value from upstream value using `map_index` of the downstream task. But when there is a difference like upstream has 2 mapped task where None and 1 is returned for `map_index=0` and `map_index=1` respectively then the downstream task only has to process value of upstream task at map_index=1 but the downstream task starts with map_index=0 and goes on to again fetch xcom value for `map_index=0` which is None. I guess some change has to be made at below code that gets the index to search in LazyXComSequence. But I guess this is a high priority issue for the next release since filter doesn't seem to be working on basic use cases. cc: @ashb for help since the dynamic task mapping was implemented by Ash and will have better idea. https://github.com/apache/airflow/blob/6a3bc01907b42aa67475ba0361d6b137f8fb51f6/task-sdk/src/airflow/sdk/definitions/_internal/expandinput.py#L165-L181 -- 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]
