duglin
commented
1 month ago Proposal:
- define an optional "compatibility" attribute in the core spec for Resources, non-strict enum
- default it to "unknown"
- implementations (or specs) can change the enum to make it strict, add values, or limit it to just a subset
values - taken from: https://docs.confluent.io/platform/current/schema-registry/fundamentals/schema-evolution.html#compatibility-types
Talk about what each means in general terms, not too specific (e.g. delete fields is too detailed).
Provide a "compatibility" type of flag on the group (or resource) to indicate what type of compatibility checking (if any) the system should do. See: https://docs.confluent.io/platform/current/schema-registry/fundamentals/schema-evolution.html#compatibility-types for some options