You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 2, 2023. It is now read-only.
The schema registry running locally on the docker image with tag 5.2.0 is not returning correct schema compatibility responses for protobuf schemas.
What happens is that when I register a schema A, whatever schema I compare with returns compatibility: true, even if it is an empty one, whereas my expectations is that it should return false, since the changes are non backwards nor forward compatible...
Is this feature not supported yet using docker image or am I missing any concept?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The schema registry running locally on the docker image with tag
5.2.0
is not returning correct schema compatibility responses for protobuf schemas.What happens is that when I register a schema
A
, whatever schema I compare with returnscompatibility: true
, even if it is an empty one, whereas my expectations is that it should returnfalse
, since the changes are non backwards nor forward compatible...Is this feature not supported yet using docker image or am I missing any concept?
The text was updated successfully, but these errors were encountered: