Fixed Issues in Schema Registry

Review the list of Schema Registry issues that are resolved in Cloudera Runtime 7.3.1, its service packs and cumulative hotfixes.

Cloudera Runtime 7.3.1.400 SP2

There are no fixed issues in this release.

There are no fixed issues in this release.

CDPD-79108: The KerberosBasicAuthenticationHandler used by Schema Registry and Streams Messaging Manager can not handle colon in password: 7.3.1.200; The KerberosBasicAuthenticationHandler is now capable of handling colons in passwords.

There are no fixed issues in this release.

OPSAPS-68708: Schema Registry might fail to start if a load balancer address is specified in Ranger: 7.3.1; Schema Registry now always ensures that the address it uses to connect to Ranger ends with a trailing slash (/). As a result, Schema Registry no longer fails to start if Ranger has a load balancer address configured that does not end with a trailing slash.
CDPD-60160: Schema Registry Atlas integration does not work with Oracle databases: 7.3.1; The Schema Registry Atlas integration works correctly when Oracle is used as the database of Schema Registry.
CDPD-58990: The getSortedSchemaVersions method should order by version number and not by schemaVersionId: 7.3.1; Schemas are ordered correctly by their version number during validation instead of their ID number.
CDPD-58949: Schemas are deduplicated during import: 7.3.1; Importing works correctly and Schema Registry does not deduplicate imported schema versions.
CDPD-59015: Schema Registry does not create new versions of schemas even if the schema is changed: 7.3.1; The new fingerprinting version solves this issue.