title: How to create/simulate creation of deserialization exception when using schema registry ( in addition to brokers and zookeepers)
body: <p>We are using spring-kafka-2.2.7.RELEASE to produce and consume avro messages and using schema registry for schema validation with 'FORWARD_TRANSITIVE' as the compatibility type.  Now, I'm trying to use 'ErrorHandlingDeserializer2 ' from spring-kafka to handle the exception/error when a deserializer fails to deserialize a message. Now I'm trying to write a component test to test this configuration. My component test expected to have below steps.</p>
  
  <ol>
  <li><p>Spin up a local kafka cluster using docker containers</p></li>
  <li><p>Send an avro message (using KafkaTemplate) with invalid schema to re-create/simulate the deserialization exception onto a test topic  </p></li>
  </ol>
  
  <p>Now what's happening is, since we have schema registry in place, if i send a message with new schema (invalid schema) it's validating the schema as per the compatibility type setting we have and not letting me producer the message onto kafka by throwing an exception at the producer level itself.</p>
  
  <p>Now my question is, In this scenario, how can I create/simulate the creation of deserialization exception to test my configuration. Please suggest.</p>
  
  <p>Note:- I don't want to disable/stop schema registry because that wouldn't simulate our prod setup.</p>