From 974d8775e283e5512892e4a2af9bbd4ca5e6c9a3 Mon Sep 17 00:00:00 2001 From: Keith Wall Date: Tue, 28 Jul 2026 17:25:50 +0100 Subject: [PATCH] docs: update schema validation use case to include Avro and Protobuf Remove the JSON Schema-only limitation from the schema validation use case page. The Record Validation filter now supports JSON Schema, Apache Avro and Protocol Buffers (Protobuf) schema types. Fixes: kroxylicious/kroxylicious#3826 Assisted-by: Claude Opus 4.6 Signed-off-by: Keith Wall --- _use_cases/schema_validation_and_enforecement.markdown | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/_use_cases/schema_validation_and_enforecement.markdown b/_use_cases/schema_validation_and_enforecement.markdown index 7f43d656..0249623c 100644 --- a/_use_cases/schema_validation_and_enforecement.markdown +++ b/_use_cases/schema_validation_and_enforecement.markdown @@ -68,8 +68,8 @@ even if producing applications are misconfigured. The filter currently supports two modes of operation: -1. Schema validation[^1] validates the content of the record against a schema. Use this for topics which have an entry in - the Schema Registry. +1. Schema validation validates the content of the record against a schema. Use this for topics which have an entry in + the Schema Registry. Supported schema types include JSON Schema, Apache Avro and Protocol Buffers (Protobuf). 2. SyntacticallyCorrectJson validation ensures the producer is producing messages that contain syntactically valid JSON. Use for topics which do not have registered schemas. @@ -90,6 +90,3 @@ The following sequence diagram shows how schema validation issues are reported b The filter accepts configuration that allows you to assign validators on a per-topic basis. There are also configuration options that allow you to define whether the filter rejects just the records that don't meet the requirements of the validator, or whether then whole batch should be returned. - - -[^1]: Currently, the feature supports only the JSON-Schema schema type.