Repository navigation
Avoid malformed XML in S3 layer deletion - #2040
Merged
echeipesh merged 1 commit intoMar 2, 2017
Merged
Conversation
During failed ingests, metadata will often be written out despite no data having been written for the layer that metadata specifies. By ensuring that S3 deletion requests are only generated for non-empty listings, we can avoid this Exception.
moradology
changed the title
echeipesh
approved these changes
Mar 2, 2017
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
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.
During failed ingests, metadata will often be written out despite no data having been written for the layer that metadata specifies. The trace such an attempted deletion causes:
Exception in thread "main" com.amazonaws.services.s3.model.AmazonS3Exception: The XML you provided was not well-formed or did not validate against our published schema.By ensuring that S3 deletion requests are only generated for non-empty listings, we avoid this Exception.