feat(table-topic): Support schema resolution from registry[WIP] #2749
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
Gezi-lzq
requested review from
superhx,
1sonofqiu and
woshigaopp
as code owners
Gezi-lzq
changed the title
Gezi-lzq
force-pushed
the
feat/schema-resolver
branch
from
c54210e to
8c551d7
Compare
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 PR enables Table Topics to support Protobuf messages that lack an embedded schema ID, allowing users to adopt this feature without modifying their existing data producers.
A new
schema_latestoption for theautomq.table.topic.schema.typetopic config activates this behavior. When set, the broker fetches the latest schema directly from the Schema Registry.The implementation uses a
SchemaResolutionResolverstrategy pattern to handle both the new registry-based resolution and the existing header-based resolution.Fixes #2739