SMT to Insert Source Partition/Offset Metadata into Headers #14
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
davidsloan
changed the title
andrewstevenson
approved these changes
Jun 21, 2024
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.
This pull request introduces the
InsertSourcePartitionOrOffsetValueKafka Connect transformation, designed to insert headers based on partition or offset values fromSourceRecords. Users can configureoffset.fieldsandpartition.fieldsto specify which fields to extract as headers, with optional prefixes (offset.prefixandpartition.prefix) for header keys. This transformation enhances metadata management by allowing seamless integration of partition and offset data into Kafka records, facilitating better downstream processing and analysis.(I also tweaked the pom to allow java 11 because being limited to 1.8 features was truly unbearable.)