Schema Registry & Data Governance
Inspect registered Avro and JSON schemas, decode Confluent wire-format payloads, and validate messages before publishing.
EventOre integrates with Confluent Schema Registry, Apicurio Registry, and local schema caches. Binary Avro payloads prefixed with the 5-byte Confluent wire-format header are automatically parsed, decoded, and rendered as formatted JSON in Live Streams and Destination Browsers.
Confluent wire-format decoding
0x00 (1 byte) + Schema ID (4 bytes, big-endian) + Binary PayloadWhen EventOre reads a message with magic byte 0x00, it extracts the 4-byte schema ID, queries the schema cache or registry endpoint, and deserializes the binary payload using the retrieved Avro schema. Non-schema binary messages fall back to transparent base64 encoding with contentType: application/base64.
Schema Registry REST API
EventOre exposes dedicated schema governance endpoints under /api/v1/schemas:
# List all cached schemas
curl http://localhost:8080/api/v1/schemas
# Retrieve schema details by ID
curl http://localhost:8080/api/v1/schemas/101?registryUrl=http://localhost:8081
# Generate a sample JSON payload template matching the Avro schema
curl http://localhost:8080/api/v1/schemas/101/template
# Validate a JSON payload against schema rules before publishing
curl -X POST http://localhost:8080/api/v1/schemas/101/validate \
-H "Content-Type: application/json" \
-d '{"payload":"{\"orderId\":\"ORD-101\",\"amount\":49.99,\"currency\":\"USD\"}"}'Register a new schema
Register local or remote schemas directly via the console or REST API:
curl -X POST http://localhost:8080/api/v1/schemas \
-H "Content-Type: application/json" \
-d '{
"schemaId": 101,
"subject": "orders-value",
"schemaType": "AVRO",
"schemaContent": "{\"type\":\"record\",\"name\":\"Order\",\"fields\":[{\"name\":\"orderId\",\"type\":\"string\"},{\"name\":\"amount\",\"type\":\"double\"},{\"name\":\"currency\",\"type\":\"string\"}]}"
}'Schema-aware publishing
When publishing to schema-bound destinations:
- Template Autocomplete: Fetch
/schemas/{id}/templateto populate default values and required record fields in the UI publisher dialog. - Pre-flight Validation: Test client inputs against the target schema with
/schemas/{id}/validate. The API reports exact field errors (missing required field, type mismatch) before emitting any bytes to the broker. - Automatic Magic Header: When publishing an Avro schema ID, the backend encodes the 5-byte header transparently.
Next: Kafka guide · PII data masking · DLQ & message redrive.