Fixed Issues in Schema Registry
Review the list of Schema Registry issues that are resolved in Cloudera Runtime 7.2.18.
- CDPD-56890: New schemas cannot be created following an upgrade
- Schemas can be created again after an upgrade even if the latest version of the schema was deleted before the upgrade.
- CDPD-58265: Schema Registry Client incorrectly applies SSL configuration
- The Cloudera distributed Schema Registry Java client applies the SSL configurations correctly even with concurrent access in Jersey clients.
- CDPD-49470: Schema Registry Client retries requests more than the configured maxAttempts when multiple URLs are used
- The Cloudera distributed Schema Registry Java client handles each request as one attempt, and does not attempt more retries based on the number of Schema Registry server URLs anymore.
- OPSAPS-68139: Schema Registry does not apply cluster wide Kerberos principal mapping by default
- The Schema Registry Kerberos Name Rules property is now empty by default. Schema Registry now automatically applies the cluster-wide auth-to-local (ATL) rules by default. During an upgrade, the previously configured value is preserved. If you have been using the default or a custom value, you must manually clear the property following an upgrade to transition to the new default value.
- CDPD-55381: Schema Registry issues authentication cookie for the authorized user, not for the authenticated one
- Schema Registry authentication cookie contains the correct authenticated user, even if the authenticated and the authorized users are different. Authenticated and authorized users can be different in scenarios where Schema Registry is used behind Knox.
- CDPD-60160: Schema Registry Atlas integration does not work with Oracle databases
- The Schema Registry Atlas integration works correctly when Oracle is used as the database of Schema Registry.
- CDPD-59015: Schema Registry does not create new versions of schemas even if the schema is changed
- The new fingerprinting version introduced in Cloudera Runtime 7.2.18 solves this issue.
- CDPD-58990: The getSortedSchemaVersions method should order by version number and not by schemaVersionId
- Schemas are ordered correctly by their version number during validation instead of their ID number.
- CDPD-58949: Schemas are deduplicated during import
- Importing works correctly and Schema Registry does not deduplicate imported schema versions.
