Enhancing Schema Version Management with Tag-Based Lookup Feature #318
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 #, if available: None
Description of changes:
Introducing tag-based lookup for schema versions to address 'poison pill' issues. Previously, recreating a schema or its version post-deletion resulted in altered UUIDs for schema versions, leading to 'poison pill' records in MSK due to deserialization failures. This update enables schema version lookup via metadata keys instead of UUIDs. When tag-based lookup is activated in the configuration, the system performs a metadata search for matching tags, subsequently using the appropriate schema version. This enhancement reduces the occurrence of 'poison pill' records by enabling schema lookup in scenarios where the schema is recreated post-deletion or redeployed via version control as part of disaster recovery processes.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.