Behavioral Changes in Schema Registry

Functional adjustments and behavioral updates for Schema Registry are introduced in Cloudera Runtime 7.3.2, its service packs, and cumulative hotfixes.

Cloudera Runtime 7.3.2.10000 SP1

Legacy TLS protocol and cipher settings replaced when TLS advanced control is enabled: Previous behavior:
You configured TLS protocol versions and cipher suites for the Schema Registry REST port using schema.registry.ssl.supportedProtocols, schema.registry.ssl.excludedProtocols, schema.registry.ssl.supportedCipherSuites, and schema.registry.ssl.excludedCipherSuites properties in Cloudera Manager.; New behavior:
When you enable the TLS_ADVANCED_CONTROL feature flag, Cloudera Manager hides the legacy supported and excluded properties and replaces them with schema.registry.ssl.allowedProtocols and schema.registry.ssl.allowedCipherSuites. These properties default to the centralized Cloudera Manager TLS settings. Custom exclude lists no longer apply when the flag is enabled. Cloudera Manager does not automatically migrate custom values. Review your TLS configuration before you enable the flag.

Cloudera Runtime 7.3.2.100 CHF 1

There are no behavioral changes in this release.

Cloudera Runtime 7.3.2

Component-level custom Java home configuration removed

Previous behavior:

You could configure a component-specific Java home for Schema Registry.

New behavior:

The component-level custom Java home configuration options are removed. Schema Registry now uses the host-level java_home configuration. If you previously set a component-specific Java home for this service, verify the host-level java_home setting after upgrading.

Schema Registry now defaults to IPv4-only communication

The default value of the schema.registry.additional.java.options configuration parameter was updated to set the IP protocol to IPv4.

If you changed the default value of this parameter before upgrading, the new default value is not applied on upgrade. You can apply it manually after the upgrade.