uranusjr opened a new pull request, #22849: URL: https://github.com/apache/airflow/pull/22849
Fix #22833. This needs two changes. First, when the upstream pushes the return value to XCom, we need to identify that the pushed value is not used on its own, but only aggregated with other return values from other mapped task instances. Fortunately, this is actually the only possible case right now, since we have not implemented support for depending on individual return values from a mapped task (aka nested mapping). So we instead skip recording any TaskMap metadata from a mapped task to avoid the problem altogether. The second change is for when the downstream task is expanded. Since the task depends on the mapped upstream as a whole, we should not use TaskMap from the upstream (which corresponds to individual task instances, as mentioned above), but the XComs pushed by every instance of the mapped task. Again, since we don't nested mapping now, we can cut corners and simply check whether the upstream is mapped or not to decide what to do, and leave further logic to the future. -- 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]
