KAFKA-18967: Add schema checker evolution tests - #22946
Open
lh0156 wants to merge 1 commit into
Open
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
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.
Summary
MetadataSchemaCheckerToolentry point.Motivation
KAFKA-18967 asks for tests that exercise the metadata schema checker beyond comparing a schema with itself. The new cases cover the field-pair iteration and per-message struct registries involved in the KAFKA-18955 fixes. While adding the coverage, the tests exposed a remaining false positive where
FieldSpecPairIteratordropped an unmatched field after avoiding the previous infinite loop.Validation
./gradlew :generator:test --no-build-cache --console=plain