[log] Fix Lz4ArrowCompressionCodec gets stuck during compression and is unable to flush data error #465
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
…is unable to flush data error
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.
Purpose
Linked issue: #463
Currently, if we try to use FRAME_LZ4 codec in flink job to do compress. The
Lz4ArrowCompressionCodecgets stuck in theFramedLZ4CompressorOutputStreamduring compression and is unable to flush data.In this pr, we try to introduce a new compress inputsStream/decompress outputStream way refer to Kafka.
Tests
API and Format
Documentation