AWS: Fix GlueCatalog: Add suppressed exception when rollback fails. Throw iceberg AlreadyExistsException rather than aws version#17122
Open
jamespfaulkner wants to merge 1 commit into
Conversation
…hrow iceberg AlreadyExistsException rather than aws version
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
1 participant
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.
Hey folks.
This addresses a couple of small bugs in
GlueCatalog.renameTableCorrect exception
When the destination table name already exists, an Iceberg
AlreadyExistsExceptionis thrown rather than the glue variation.Original Exception lost during rollback
In the failure case, when rolling back the new table creation, if that also fails the original exception is lost. They are both now included in the throws with the use of addSuppress.