Handle the case when LogUri is missing in EMR response #31485
Closed
Conversation
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
When EMR describe-cluster, does not have LogURI information, we should silently skip persisting the link to XCom rather than fail on KeyError. Fixes: apache#31480
boring-cyborg
bot
added
area:providers
provider:amazon
Contributor
|
#31482 also attempts to address the issue |
Member
Author
|
The other one is likely nicer. I did not have possibllity to test mine, and I was not sure how to "disable" the link in the BaseAWSLink so I took the "safe" route - but I am happy to close mine in favour of #31482 if that's tested one. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
When EMR describe-cluster, does not have LogURI information, we should silently skip persisting the link to XCom rather than fail on KeyError.
Fixes: #31480
^ 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.