Skip to content

Conversation

crepererum
Copy link
Collaborator

While we technically don't want to emit compressed data for IOx, I'm worried that some backup / cluster tool will compress our messages anyways and we end up in some incident not being able to read the data any longer.

The primary contribution of this PR is to figure out how compression works. Adding more types can be done later and should be rather easy, since they all follow the same pattern (i.e. a compressed block that follows the number of records).

@crepererum crepererum requested a review from tustvold January 25, 2022 11:56
@crepererum crepererum force-pushed the crepererum/gzip_compression branch 2 times, most recently from e344242 to 0a7aeda Compare January 25, 2022 12:11
Copy link
Contributor

@carols10cents carols10cents left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

- Also capture content from `log` crate
- Play nice w/ Rust's libtest message capture
@crepererum crepererum force-pushed the crepererum/gzip_compression branch from 0a7aeda to 290991e Compare January 31, 2022 16:54
@crepererum crepererum added the automerge Instruct kodiak to merge the PR label Jan 31, 2022
@crepererum crepererum force-pushed the crepererum/gzip_compression branch from 290991e to cc23297 Compare January 31, 2022 17:03
@crepererum crepererum force-pushed the crepererum/gzip_compression branch from cc23297 to c3f9bf2 Compare January 31, 2022 17:04
@kodiakhq kodiakhq bot merged commit 9d1ddd9 into main Jan 31, 2022
@mkmik mkmik deleted the crepererum/gzip_compression branch February 1, 2022 10:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automerge Instruct kodiak to merge the PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants