Schema validation in producers in Kafka - Step-by-Step Execution

Process Flow - Schema validation in producers

Start Producer

↓

Prepare Message

↓

Validate Message Against Schema

↓

Send

↓

Message Sent

↓

End Producer

The producer prepares a message, checks it against the schema, sends it if valid, or rejects it if invalid.

Execution Sample

Kafka

producer.send({"name": "Alice", "age": 30})
# Validate message schema
# If valid, send
# Else, raise error

This code sends a message after checking it matches the schema.

Process Table

Step	Action	Message Content	Schema Valid?	Result
1	Prepare message	{"name": "Alice", "age": 30}	N/A	Message ready
2	Validate message	{"name": "Alice", "age": 30}	Yes	Validation passed
3	Send message	{"name": "Alice", "age": 30}	Yes	Message sent
4	Prepare message	{"name": "Bob", "age": "thirty"}	N/A	Message ready
5	Validate message	{"name": "Bob", "age": "thirty"}	No	Validation failed - reject message
6	Stop sending	{"name": "Bob", "age": "thirty"}	No	Error raised, message not sent

💡 Producer stops sending when message fails schema validation.

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5	After Step 6
message	null	{"name": "Alice", "age": 30}	{"name": "Alice", "age": 30}	sent	{"name": "Bob", "age": "thirty"}	{"name": "Bob", "age": "thirty"}	error
validation_status	null	pending	valid	sent	pending	invalid	error

Key Moments - 3 Insights

Why does the producer reject the message with age as a string?

Because the schema expects 'age' to be a number, not a string. This is shown in execution_table rows 4 and 5 where validation fails.

What happens if the message passes schema validation?

The message is sent to Kafka as shown in execution_table row 3, where validation_status is 'valid' and result is 'Message sent'.

Does the producer send any message after validation fails?

No, as shown in execution_table row 6, the producer raises an error and stops sending the invalid message.

Visual Quiz - 3 Questions

Look at the execution table, what is the validation status after step 2?

A invalid

B pending

C valid

D error

💡 Hint

Check the 'validation_status' variable after step 2 in variable_tracker.

At which step does the producer reject the message due to schema mismatch?

A Step 5

B Step 3

C Step 2

D Step 6

💡 Hint

Look at execution_table rows where 'Schema Valid?' is 'No'.

If the message had age as 25 (number), how would the validation result change at step 5?

A No change, still invalid

B Validation would pass

C Validation would fail

D Producer would raise error

💡 Hint

Refer to execution_table rows 2 and 5 comparing valid and invalid age types.

Concept Snapshot

Schema validation in producers:
- Producer prepares message
- Checks message against schema
- If valid, sends message
- If invalid, rejects and raises error
- Prevents bad data from entering Kafka

Full Transcript

Schema validation in Kafka producers means the producer checks each message against a predefined schema before sending it. If the message matches the schema, it is sent to Kafka. If not, the producer rejects the message and raises an error. This prevents invalid data from entering the system. For example, if the schema expects 'age' as a number, sending a string will cause validation to fail and the message will not be sent. This process ensures data quality and consistency in Kafka topics.

Practice

1. What is the main purpose of schema validation in Kafka producers?

easy

A. To compress messages for storage

B. To speed up message delivery in Kafka

C. To ensure data sent matches the expected format and structure

D. To encrypt messages before sending

Solution

1. Step 1: Understand schema validation role

   Schema validation checks if data matches a predefined format or structure.

2. Step 2: Identify producer's goal

   Producers use schema validation to keep data clean and consistent before sending.

3. Final Answer:

   To ensure data sent matches the expected format and structure -> Option C

4. Quick Check:

   Schema validation = data format check [OK]

Hint: Schema validation means checking data format before sending [OK]

Common Mistakes:

• Confusing validation with encryption
• Thinking it speeds up message delivery
• Assuming it compresses data

2. Which configuration is essential for KafkaAvroSerializer to validate schemas in a producer?

easy

A. bootstrap.servers

B. schema.registry.url

C. acks

D. compression.type

Solution

1. Step 1: Identify serializer requirements

   KafkaAvroSerializer needs to connect to the schema registry to validate schemas.

2. Step 2: Find the required config key

   The key 'schema.registry.url' tells the serializer where to find the schema registry.

3. Final Answer:

   schema.registry.url -> Option B

4. Quick Check:

   Schema registry URL = validation source [OK]

Hint: Set schema.registry.url for schema validation [OK]

Common Mistakes:

• Using bootstrap.servers for schema validation
• Confusing acks with schema config
• Missing schema.registry.url causes validation failure

3. Given this producer code snippet using KafkaAvroSerializer:

props.put("schema.registry.url", "http://localhost:8081");
ProducerRecord record = new ProducerRecord<>("topic", userRecord);
producer.send(record);

What happens if userRecord does not match the registered schema?

medium

A. A serialization exception is thrown and message is not sent

B. The producer retries sending the message indefinitely

C. The message is sent successfully without validation

D. The message is sent but schema registry logs a warning

Solution

1. Step 1: Understand KafkaAvroSerializer behavior

   It validates data against the schema before sending.

2. Step 2: Check what happens on mismatch

   If data doesn't match, serialization fails and an exception is thrown, preventing send.

3. Final Answer:

   A serialization exception is thrown and message is not sent -> Option A

4. Quick Check:

   Schema mismatch = serialization error [OK]

Hint: Mismatch triggers serialization exception, no send [OK]

Common Mistakes:

• Assuming message sends without validation
• Thinking producer retries endlessly
• Believing only warnings are logged

4. You see this error when sending a message: io.confluent.kafka.schemaregistry.client.rest.exceptions.RestClientException: 404 Not Found. What is the most likely cause related to schema validation?

medium

A. The schema registry URL is incorrect or unreachable

B. The producer topic does not exist

C. The message key is null

D. The Kafka broker is down

Solution

1. Step 1: Analyze the error message

   404 Not Found means the client can't reach the schema registry endpoint.

2. Step 2: Connect error to schema validation

   If schema registry URL is wrong or server is down, validation fails with this error.

3. Final Answer:

   The schema registry URL is incorrect or unreachable -> Option A

4. Quick Check:

   404 error = schema registry URL issue [OK]

Hint: 404 error means schema registry URL problem [OK]

Common Mistakes:

• Blaming topic existence for 404
• Assuming null key causes this error
• Thinking Kafka broker down causes 404

5. You want to produce messages with optional fields that may or may not be present in your Avro schema. How should you configure your producer and schema to allow schema validation to pass when some fields are missing?

hard

A. Send empty strings for missing fields to pass validation

B. Remove optional fields from the schema and send messages without them

C. Disable schema validation in the producer configuration

D. Define optional fields with default values in the Avro schema and use KafkaAvroSerializer with schema.registry.url set

Solution

1. Step 1: Understand optional fields in Avro

   Optional fields must have default values in the schema to allow missing data.

2. Step 2: Configure producer for validation

   Use KafkaAvroSerializer with schema.registry.url set to validate against schema with defaults.

3. Final Answer:

   Define optional fields with default values in the Avro schema and use KafkaAvroSerializer with schema.registry.url set -> Option D

4. Quick Check:

   Defaults + serializer config = optional fields allowed [OK]

Hint: Use defaults in schema for optional fields [OK]

Common Mistakes:

• Removing fields instead of using defaults
• Disabling validation instead of fixing schema
• Sending empty strings instead of omitting fields