feat(kafka source): add decompression option for producer-compressed payloads - #26024
Open
cjford wants to merge 6 commits into
Open
feat(kafka source): add decompression option for producer-compressed payloads#26024cjford wants to merge 6 commits into
cjford wants to merge 6 commits into
Conversation
Contributor
|
All contributors have signed the CLA ✍️ ✅ |
Author
|
I have read the CLA Document and I hereby sign the CLA |
This file contains hidden or 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.
Summary
Adds
decompressionconfig option to kafka sources. This allows unwrapping of application-level (not kafka protocol-level) compression from message payloads, so that their original forms can be used for framing/decoding and downstream components. Supportsgzip,zlib, andzstdalgorithms, and furthermore allows optional zstddictionary_pathif one was used during compression.On decompression failure, a component error is logged and the message skipped. Its offset is still committed so that partition consumption continues, which is consistent with existing behavior for decoding failures.
This pattern should be re-usable for other sources, but needs some wiring in each including specific failure behavior. I also explored more general alternative implementations (e.g. decompression as part of framing, separate pre-framing Decoder step), but found them not workable universally, particularly with streaming inputs.
Code generated using Claude Fable 5
Vector configuration
How did you test this PR?
Tested manually with local (macOS aarch64) kafka/vector setup, using
zstdto compress raw messages,kcatto publish them to kafka, and a console sink to verify output. Covered various scenarios:Is this a breaking change?
Does this PR include user facing changes?
no-changeloglabel to this PR.References