Table renames: allow delete-op after put-op #6892
Merged
Conversation
This file contains 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
`CommitImpl#commitAddOperations` currently expects that `Operation.Delete`s appear before `Operation.Put`s (rename table use case). This is not necessary. Iceberg's Nessie catalog submits the operations in the "wrong order" (delete after put), which currently fails in Nessie with a conflict exception. This change makes Nessie resilient against this issue.
adutra
approved these changes
May 25, 2023
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.
CommitImpl#commitAddOperationscurrently expects thatOperation.Deletes appear beforeOperation.Puts (rename table use case). This is not necessary. Iceberg's Nessie catalog submits the operations in the "wrong order" (delete after put), which currently fails in Nessie with a conflict exception. This change makes Nessie resilient against this issue.