-
Notifications
You must be signed in to change notification settings - Fork 593
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[v24.2.x] CORE-6860 Schema Registry: add detailed verbose compatibility checks #23110
[v24.2.x] CORE-6860 Schema Registry: add detailed verbose compatibility checks #23110
Conversation
// There must be a compatible reader message for every writer | ||
// message |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this doesn't appear in the upstream diff. no clue why 😕
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I must have formatted the file while resolving the merge conflict which shifted the last word to a new line. I've fixed this now to match the original PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm modulo that weird code comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, aside from the comment
(cherry picked from commit 4c87c5e)
When an incompatible schema is posted, include the verbose compatibility messages in the error message. This helps users understand the reason for the incompatibility and it matches the reference implementation. Includes a minor fix to the way the compatibility level message is formatted. (cherry picked from commit cda768b)
0a97039
to
51ff964
Compare
Force-push: fix comment formatting |
Backport of PR #22958
Fixes #23107
Fixes https://redpandadata.atlassian.net/browse/CORE-7073
Conflicts:
proto_compatibility_result check_compatible(std::filesystem::path)
in 4520d58. The commits should be identical to the one being cherry-picked.