-
Notifications
You must be signed in to change notification settings - Fork 2.2k
enhancement(kafka source): add support for consuming records with null bodies #25625
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
nviliunov-evolution-throwaway
wants to merge
3
commits into
vectordotdev:master
Choose a base branch
from
nviliunov-evolution-throwaway:null-kafka-bodies
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+163
−10
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| Added a new `ignore_tombstones` option to the `kafka` source. When set to `false`, Kafka tombstone messages (records with a `null` payload) are no longer skipped and instead produce an event, allowing pipelines to consume messages where only the key, headers, or other metadata are needed. Defaults to `true` to preserve the existing behavior. |
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When
ignore_tombstones = falseis combined with a metric-only decoder such asdecoding.codec = "influxdb",KafkaSourceConfig::outputs()still advertises onlyself.decoding.output_type()(Metric), but this branch emits anEvent::Log. The topology will therefore accept metric-only downstream components, which filter out log arrays, and reject log-only consumers as a data-type mismatch, so tombstone records produced here cannot be consumed in those metric pipelines. IncludeDataType::Login the source output type when this option can emit tombstones, or reject metric-only decoders for this mode.Useful? React with 👍 / 👎.