Ensures the Ion 1.1 managed writer does not close its OutputStream twice. #940
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
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.
Description of changes:
Before this change, the Ion 1.1 managed text writer would close its OutputStream twice: once when closing its system-level raw writer and once when closing its user-level raw writer. This was not caught by tests because they used ByteArrayOutputStream, whose close() implementation does nothing. Other OutputStreams like FileOutputStream do not tolerate being written to (in this case, by the user-level raw writer) after close.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.