uranusjr opened a new pull request, #76826: URL: https://github.com/apache/airflow/pull/76826
Get XCom with no map index reads map index -1. A mapped task has no -1 row, so the read finds nothing. #76825 works around this on the client side for older servers. This PR fixes it in the Execution API. From API version 2027-02-28, the server resolves an omitted map index from the producing task's definition in its Dag: | Producing task | Map index | Result | |---|---|---| | Not mapped | omitted | Its value | | Mapped, or in a mapped task group | omitted | Every instance's value as a list, the same values as the slice endpoint, including with `include_prior_dates` (`[]` if there are none) | | Any | an int | That instance's value, or not found (unchanged) | `map_index` becomes optional on `GetXcomFilterParams`. Older API versions keep reading -1 for an omitted map index. With a server that has this fix, #76825's fallback never triggers, and a mapped task with no values results in an empty list instead of null. -- 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]
