Symptoms
The running Kafka consumer continues to see messages that don’t match the configured schema even though the schema filtering control has been added to the option. Also, the consumer continues to see messages with fields that should have redacted values as configured in the redaction control.
Causes
When the first redaction or schema filtering control is added to an option that is being used in an active Kafka consumer, the changes are not automatically picked up by that consumer.
Resolving the problem
To resolve the problem, disconnect and reconnect the consumer.