This repository has been archived by the owner on Apr 13, 2022. It is now read-only.
Somi minor fixes to make it more robust #5
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
…et == 0, the minimal offset is requested from the consumer. And added a 'dirty' way to print stactraces in the worker threads
…our usecase) for 40% reduction on storage-costs
|
just addes support for compressions (gzip) |
Work with Environment Variables in properties, and Kafka 0.7.2
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
the minimal offset is requested from the consumer, instead of 0 at first run. This will enable the backup to actually work if the persistent logs have been rotated (default a week)
And added a 'dirty' way to print stactraces in the worker threads, which die if the getKafkaMaxMessageSize value is smaller than the actual message.payload.remaining()