-
Notifications
You must be signed in to change notification settings - Fork 269
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
Implementation of BACKWARD_TRANSITIVE, FORWARD_TRANSITIVE might be incorrect #1239
Labels
type/question
Further information is requested
Comments
Thoughts @jsenko ? |
The standard definition of transitivity is |
I found other issues in the current master, I'm working on a PR. |
I recommend you do any work against the |
jsenko
added a commit
to jsenko/apicurio-registry
that referenced
this issue
Feb 24, 2021
EricWittmann
pushed a commit
that referenced
this issue
Feb 24, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
My understanding of transitive compatibility modes (BACKWARD_TRANSITIVE, FORWARD_TRANSITIVE) is that schema registry ensures that the updated schema version is compatible with all the versions in the registry.
However, the code in JsonSchemaCompatibilityChecker checks compatibility between old versions.
Current behavior:
Expected behavior:
Is my understanding correct?
The text was updated successfully, but these errors were encountered: