Cloudera Schema Registry
docs.cloudera.com
- Linux
- Web
- API
- Self-hosted
What Cloudera Schema Registry is
Cloudera Schema Registry is a shared repository for schemas used by streaming applications. It stores schemas centrally so applications can validate event data, while identifiers, versions, and searchable metadata help teams manage producer and consumer format changes. Avro and JSON schemas are supported, including Avro logical types. Compatibility checks can be backward, forward, full, or disabled. The REST API handles schema and version management, imports and exports, searches, aggregation, and Confluent-compatible endpoints. A Kubernetes Operator edition packages Cloudera Runtime Schema Registry as a Helm chart. Integration points include custom NiFi processors and Kafka serializers and deserializers. Metadata storage supports MySQL, PostgreSQL, and Oracle; serializer and deserializer JARs can use local filesystems or HDFS. TLS can protect application, client, OAuth, and database traffic. Secure Kubernetes installation uses authentication, authorization, channel encryption, and OAuth with an external server. The UI is limited to unauthenticated technical previews or development environments.
Who it suits
It suits teams running streaming applications that need shared schema management, validation, and controlled message-format evolution.
Good to know, and what to watch
- Supports Avro and JSON schemas
- Provides configurable compatibility modes
- REST API includes import, export, and search
- Deploys on Kubernetes through a Helm chart
- Integrates with NiFi and Kafka serializers
- Production secure use should rely on the REST API
- UI does not support OAuth login
- Kubernetes installation requires a valid Cloudera license
- Pricing is available only on request
Plans
Every plan and priceStreams Messaging
Pricing on request
The verdict
Cloudera Schema Registry centralizes schema governance for streaming systems and offers flexible APIs, storage, and deployment options. Teams should account for the UI’s authentication limitation and licensing prerequisites.
What the maker publishes
- API
- Its REST API supports schema and version management, file import and export, search, aggregation, and Confluent-compatible endpoints. source
- Authentication and authorization
- The documented secure Kubernetes installation configures authentication, authorization, and channel encryption, and uses OAuth authentication with an external OAuth server. source
- Deployment
- The Kubernetes Operator edition packages Cloudera Runtime Schema Registry as a Helm chart for deployment on Kubernetes. source
- Formats
- It supports Avro and JSON schemas, including Avro logical types. source
- Integrations
- Documented integration points include custom NiFi processors and Kafka serializers and deserializers. source
- Intended users
- The documentation describes the product for streaming applications that need a shared schema repository and safer evolution of producer and consumer message formats. source
- License requirement
- The documented Kubernetes installation prerequisites include access to a valid Cloudera license and credentials for Cloudera’s artifact repositories. source
- Purpose
- Schema Registry centrally stores and manages schemas for streaming data so applications can validate their data. source
- Security
- TLS can secure application, client, OAuth, and database traffic, and Cloudera recommends enabling it for all these categories. source
- Storage
- Schema metadata storage supports MySQL, PostgreSQL, and Oracle; serializer and deserializer JAR storage supports local filesystems and HDFS, with the local filesystem as default. source
- Support
- Cloudera states that its cloud and on-premises offerings include enterprise-grade technical support and version, maintenance, and security updates. source
- UI limitation
- In this release the Schema Registry UI is limited to unauthenticated technical previews or development environments because it does not support OAuth login; production environments requiring security should use the REST API. source
- Versioning
- Schemas have identifiers and can be versioned, with searchable metadata and configurable backward, forward, full, or no compatibility checks. source
Checked against the maker's pages on 2 Oct 2026.