feat[kafka]: avro offline schema handling - #8442
Open
amin-farjadi wants to merge 3 commits into
Open
Conversation
powertools-for-aws-oss-automation
Bot
added
the
size/L
boring-cyborg
Bot
added
documentation
amin-farjadi
changed the title
amin-farjadi
changed the title
amin-farjadi
force-pushed
the
feat/kafka-avro-offline-schema-prefix
branch
from
September 5, 2026 00:27
82b5409 to
e9c5f67
Compare
|
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
1 participant
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.
Issue number: closes #8385
Summary
Changes
Added a
value_schema_wire_formatarguement to theSchemaConfigof Kafka utility, enabling the use of local (packaged with lambda) AVRO value schema.User experience
An optional argument has been added to
SchemaConfig. Documentation has been updated, showing how and when this argument can be used.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.