Kafka Source in combination with Kafka Sink leads to infinite loop #65
Conversation
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
…rce will set and which kind of impacts that implicit behaviour can have.
rolandjohann
changed the title
rolandjohann
changed the title
|
Can one of the admins verify this patch? |
waidr
pushed a commit
to waidr/flume
that referenced
this pull request
Jul 24, 2019
* add clean * add clean
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.
Because Kafka Source sets some header fields - especially "topic" - this leads to unexpected behavior in combination with the Kafka Sink => The messages will be consumed and produced again into that topic until the agent will be shut down.
The Kafka Sink determines the topic to which the event should be produced to based on a header field "topic" and overwrites the configuration of the sink.
To (nearly) fix that there are multiple options: