What's New in Schema Registry

Enable SMM principal as trusted proxy user in Schema Registry

SMM usually connects to Schema Registry on behalf of an end user. For requests coming from SMM, Schema Registry can now extract and authorize the end user to authorize the request.

New fingerprint version is added to Schema Registry with configuring option

A new fingerprint version, V2, is available in Schema Registry that contains the missing schema parts from the previous version. Newly created clusters use the V2 fingerprint version. Upgraded clusters still use the V1 fingerprint version, but the Fingerprint Version property can be used to change the fingerprint version in Schema Registry. Cloudera recommends changing the fingerprint version to V2 following an upgrade. For more information on how to change the fingerprint version, see Step 9: Complete Post-Upgrade steps for upgrades to Cloudera Private Cloud Base.

This improvement fixes an issue in previous versions. For more information on the original issues as well as Schema Registry fingerprinting, see TSB-713. Note that even if you switch to V2, some issues might still persist, see TSB-718 for more information.

Support for additional JVM options

Additional JVM options can be passed to Schema Registry using the schema.registry.additional.java.options property in Cloudera Manager.