ferenc-csaky opened a new pull request, #24914:
URL: https://github.com/apache/flink/pull/24914
## What is the purpose of the change
Provides a way to handle output stream based compaction in case the data
stream is compressed via `ConcatFileCompactor`. The problem is described well
in the Jira ticket. The relevant logical changes are in
`OutputStreamBasedPartFileWriter`, where in case of a `COMPRESSED_STREAM`, now
a new recoverable writer is created instead of reusing the one that was created
for the actual application data, so if the application data is a compressed
stream, the special header bytes will not be duplicated.
## Brief change log
- Introduce new `CompactingFileWriter ` type `COMPRESSED_STREAM` .
- Add `compressed` flag to `ConcatFileCompactor` that denotes
`COMPRESSED_STREAM`.
- Handle `COMPRESSED_STREAM` in `OutputStreamBasedPartFileWriter`
appropriately.
- Changed `AbstractCompactTestBase` to `protected` to be able to use in the
new `CompactServiceTest` that is in a diff. package.
- Moved some test helper methods to `AbstractCompactTestBase` to
avoid/eliminate duplication.
## Verifying this change
- Added new unit tests for the newly introduced logic in
`CompactServiceTest`.
## Does this pull request potentially affect one of the following parts:
- Dependencies (does it add or upgrade a dependency): no
- The public API, i.e., is any changed class annotated with
`@Public(Evolving)`: no
- The serializers: no
- The runtime per-record code paths (performance sensitive): no
- Anything that affects deployment or recovery: JobManager (and its
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
- The S3 file system connector: no
## Documentation
- Does this pull request introduce a new feature? debatable
- If yes, how is the feature documented? JavaDocs
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
