Fixed Issues in Schema Registry

Fixed issues and resolved maintenance items for Schema Registry are addressed in Cloudera Runtime 7.3.2 and its associated service packs.

Cloudera Runtime 7.3.2

Cloudera Runtime 7.3.2 resolves Schema Registry issues and incorporates fixes from the service packs and cumulative hotfixes from 7.3.1.100 through 7.3.1.706. For a comprehensive record of all fixes in Cloudera Runtime 7.3.1.x, see Fixed Issues.

OPSAPS-71866: Schema Registry fails to start when schema.registry.oauth.clock.skew is set in Cloudera Manager: 7.3.2; Schema Registry failed to start when the schema.registry.oauth.clock.skew configuration property was set in Cloudera Manager. This issue is now fixed.
OPSAPS-71679: Ranger resource-based policy creation attempted on each service restart: 7.3.2; On each service restart, Kafka, Kafka Connect, and Schema Registry attempted to create Ranger resource-based policies even when the Ranger policy cache was already present. Resource-based policy creation is now skipped when the policy cache file exists, reducing unnecessary Ranger operations on restart.
CDPD-73277: Schema Registry configuration with Oracle TLS fails: 7.3.2; The TLS-related Oracle database configuration parameters no longer cause issues during the Schema Registry startup if they are set.
CDPD-94371: Schema Registry does not start with MySQL 8.4 on new installations: 7.3.2; Fixed an issue that caused startup failure on new Schema Registry installations when using MySQL 8.4.