Manage Kafka Schema Registry compatibility modes

domain: docs.confluent.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Set the global default compatibility via PUT /config with body {"compatibility": "BACKWARD"} using the Schema Registry REST API
  2. Override per-subject compatibility via PUT /config/YOUR_SUBJECT with the desired mode (BACKWARD, FORWARD, FULL, NONE, or their _TRANSITIVE variants)
  3. Register a new schema version via POST /subjects/YOUR_SUBJECT/versions with the Avro/JSON/Protobuf schema string
  4. Test compatibility before registration with POST /compatibility/subjects/YOUR_SUBJECT/versions/latest
  5. List all subjects with GET /subjects and inspect schema versions with GET /subjects/YOUR_SUBJECT/versions

Known gotchas

Related routes

Set Schema Registry compatibility mode per subject and evolve an Avro schema safely
kafka · 6 steps · unrated
Configure and validate Confluent Schema Registry subject compatibility modes before deploying a schema change
docs.confluent.io · 5 steps · unrated
Configure Confluent Schema Registry compatibility modes for JSON Schema and Protobuf subjects
data-engineering · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans