Confluent Schema Registry
Schema registryconfluent-schema-registry
Avro, Protobuf and JSON schema registry for Kafka with backward compatibility by default.
- Provider
- default
- Kind
- Schema registry
- Category
- Data
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| compatibility | enum | none | backward | forward | full | no | backward | ▸ backward |
| enforced | boolean | — | no | false | ▸ false |
| managed | boolean | — | no | false | ▸ false |
| schemaFormat | enum | avro | protobuf | json-schema | no | avro | inherited |
| subjectNameStrategy | enum | topic-name | record-name | topic-record-name | no | topic-name | inherited |
Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.
No rule reads this kind yet. That is a gap, not a guarantee.
nodes:
- { id: "confluent-schema-registry", component: "confluent-schema-registry" }# yaml-language-server: $schema=../../schema/component.schema.json # Confluent Schema Registry: Avro/Protobuf/JSON schemas per subject, backward compatibility by # default; broker-side validation is opt-in. schemaVersion: "1" type: "component" id: "confluent-schema-registry" kind: "schema-registry" provider: "default" docs: "https://docs.confluent.io/platform/current/schema-registry/index.html" defaults: compatibility: "backward" enforced: false managed: false properties: schemaFormat: type: "enum" values: ["avro", "protobuf", "json-schema"] default: "avro" subjectNameStrategy: type: "enum" values: ["topic-name", "record-name", "topic-record-name"] default: "topic-name"