Skip to main content
Quick navigation

Chaos Simulate Invalid Schema Id

This interceptor injects Schema Ids into messages, simulating a situation where clients cannot deserialize messages with the schema information provided.

This demo will run you through some of these use cases step-by-step.

View the full demo in realtime​

You can either follow all the steps manually, or watch the recording

Review the docker compose environment​

As can be seen from docker-compose.yaml the demo environment consists of the following services:

  • gateway1
  • gateway2
  • kafka-client
  • kafka1
  • kafka2
  • kafka3
  • schema-registry
cat docker-compose.yaml

Starting the docker environment​

Start all your docker processes, wait for them to be up and ready, then run in background

  • --wait: Wait for services to be running|healthy. Implies detached mode.
  • --detach: Detached mode: Run containers in the background
docker compose up --detach --wait

Creating topic with-schema on gateway1​

Creating on gateway1:

  • Topic with-schema with partitions:1 and replication-factor:1
kafka-topics \
    --bootstrap-server localhost:6969 \
    --replication-factor 1 \
    --partitions 1 \
    --create --if-not-exists \
    --topic with-schema

Adding interceptor simulate-invalid-schema-id​

Let's create the interceptor, instructing Conduktor Gateway to inject Schema Ids into messages, simulating a situation where clients cannot deserialize messages with the schema information provided.

step-06-simulate-invalid-schema-id-interceptor.json:

{
  "kind" : "Interceptor",
  "apiVersion" : "gateway/v2",
  "metadata" : {
    "name" : "simulate-invalid-schema-id"
  },
  "spec" : {
    "comment" : "Adding interceptor: simulate-invalid-schema-id",
    "pluginClass" : "io.conduktor.gateway.interceptor.chaos.SimulateInvalidSchemaIdPlugin",
    "priority" : 100,
    "config" : {
      "topic" : "with-schema",
      "invalidSchemaId" : 999,
      "target" : "CONSUME"
    }
  }
}
curl \
    --silent \
    --request PUT "http://localhost:8888/gateway/v2/interceptor" \
    --header "Content-Type: application/json" \
    --user "admin:conduktor" \
    --data @step-06-simulate-invalid-schema-id-interceptor.json | jq

Listing interceptors​

Listing interceptors on gateway1

curl \
    --silent \
    --request GET "http://localhost:8888/gateway/v2/interceptor" \
    --user "admin:conduktor" | jq

Let's produce some records to our created topic​

echo '{"message": "hello world"}' | \
kafka-json-schema-console-producer \
--bootstrap-server localhost:6969 \
--topic with-schema \
--property value.schema='{
     "title": "someSchema",
     "type": "object",
     "properties": {
       "message": {
         "type": "string"
       }
     }
   }'

Let's consume them with a schema aware consumer.​

kafka-json-schema-console-consumer \
    --bootstrap-server localhost:6969 \
    --topic with-schema \
    --from-beginning

Tearing down the docker environment​

Remove all your docker processes and associated volumes

  • --volumes: Remove named volumes declared in the "volumes" section of the Compose file and anonymous volumes attached to containers.
docker compose down --volumes

Conclusion

Yes, Chaos Simulate Invalid Schema Id is simple as it!