Documentation
Schema Registry
Schema Registries

Overview

The Schema Registries feature provides various capabilities:

  • The ability to manage multiple Schema Registry Servers.
  • Listing and Mutating sujects and subject versions.
  • Validating schema definitions and compatibility and more ...

If you're not familiar with the Schema Registry concepts, I highly recommend watching this 101 course (opens in a new tab) done by the amazing Danica Fine from Confluent.

Create Local Schema Registry

Creating a local Schema Registry Server is a simple process. You'll need to provide a name and the local Schema Registry URL.

You can customize the Schema Registry Client configuration by updating the beautified configuration, or by directly editing the raw JSON configuration.

If you want to opt for JMX metrics, you'll need to provide the full JMX URL.

Beautified Configuration

Schema Registry Local Main Configuration Image

Raw Configuration

Schema Registry Local Raw Configuration Image

JMX Configuration

Schema Registry Local JMX Configuration Image

Create Confluent Schema Registry

After creating a new confluent cluster, you can enable data governance to use the Schema Registry.

After that it's super easy to create an API Key, grab the configuration and use it to create a new Schema Registry connection in Blazing KRaft.

Enable Confluent Schema Registry

Enable Confluent Schema Registry Image

Confluent Client Configuration

Confluent Schema Registry Client Configuration Image

Blazing KRaft Configuration

Schema Registry Confluent Main Configuration Image

Create Aiven Schema Registry

After creating a new Aiven Kafka Service, you can enable the Schema Registry integration.

After that it's super easy to grab the configuration and use it to create a new Schema Registry connection in Blazing KRaft.

If you encounter the following error: Unexpected character (':' (code 58)): Expected space separating root-level values\n at [Source: (sun.net.www.protocol.http.HttpURLConnection$HttpInputStream); line: 1, column: 5]; error code: 50005, its probably because of a 404 error. Why I'm I mentioning this in the Aiven Schema Registry section? Because for now the /mode is not available in Aiven and when the confluent schema registry java client encounters an error it tries to compute an error message and it fails with the above nasty error. It has been handled in Blazing KRaft, but if you encounted it just know its a schema registry server error.

Enable Aiven Schema Registry

Enable Aiven Schema Registry Image

Aiven Client Configuration

Aiven Schema Registry Client Configuration Image

Blazing KRaft Configuration

Schema Registry Aiven Main Configuration Image

Schema Registries

After registering a Schema Registry Server, you'll be able to view the list of registered Schema Registry Servers.

Schema Registries Image

Edit Schema Registry

Edit Schema Registry Image

Delete Schema Registry

Delete Schema Registry Image

Miscellaneous

What makes Blazing KRaft blazingly fast is mainly the fact that clients are managed in memory, therefore if you're deploying multiple instances of Blazing KRaft, you need to make sure to restart the instances after Creating, Editing or Deleting a Schema Registry Server.

This is why we highly recommend that you register all your clients before horizontally scaling. But if you're deploying only one instance, you don't need to worry about that as it is already handled by the server.