Behavioral Changes in Schema Registry

Learn about the change in certain functionality of Schema Registry that has resulted in a change in behavior from the previously released version to this version of Cloudera Runtime.

Schema compatibility check now supports the evolution of Avro enums.
Previous behavior:
Schema compatibility check fails when a writer schema that has enum values is not present in the reader schema (some previous version), regardless if the reader has a default value.
New behavior:
A schema that does not have all enum values but has a default value set, remains compatible with a newer version that has an extended set of enum values.