Honor the 'ti' while deleting XComs via execution API#47895
Merged
amoghrajesh merged 1 commit intoapache:mainfrom Mar 18, 2025
Merged
Honor the 'ti' while deleting XComs via execution API#47895amoghrajesh merged 1 commit intoapache:mainfrom
amoghrajesh merged 1 commit intoapache:mainfrom
Conversation
ashb
approved these changes
Mar 18, 2025
kaxil
approved these changes
Mar 18, 2025
Contributor
Author
|
The test failure is unrelated, merging. |
agupta01
pushed a commit
to agupta01/airflow
that referenced
this pull request
Mar 21, 2025
nailo2c
pushed a commit
to nailo2c/airflow
that referenced
this pull request
Apr 4, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Teething problem cos of #45481.
The delete XCOM API should handle deletion better, we shouldnt be deleting for all "ti" with that key but honor the ti sent along with map_index.
Added a test that reflects this scenario well too.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.