Known Issues in Schema Registry
Learn about the known issues in Schema Registry, the impact or changes to the functionality, and the workaround.
- CDPD-56890: New schemas cannot be created following an upgrade
- If you delete the latest version of a schema (the one with the highest ID) from the Schema Registry database before an upgrade, you might not be able to create new schemas after you upgrade the cluster to a newer version.
- CDPD-58265: Schema Registry Client incorrectly applies SSL configuration
- The Cloudera distributed Schema Registry Java client might fail to apply the SSL configurations correctly with concurrent access in Jersey clients due to a Jersey issue related to JDK.
- CDPD-55381: Schema Registry issues authentication cookie for the authorized user, not for the authenticated one
- When the authenticated user is different from the authorized user, which can happen when Schema Registry is used behind Knox, authorization issues can occur for subsequent requests as the authentication cookie in Schema Registry stores the authorized user.