anchor.diff:  deserializationExceptionHandler::
   Deserialization error handler type.
   This handler is applied per consumer binding as opposed to the binder level property described before.
  -Possible values are - `logAndContinue`, `logAndFail` or `sendToDlq`
  +Possible values are - `logAndContinue`, `logAndFail`, `skipAndContinue` or `sendToDlq`
   +
   Default: `logAndFail`
   
  
positive.code: Deserialization error handler type.
  This handler is applied at the binder level and thus applied against all input binding in the application.
  There is a way to control it in a more fine-grained way at the consumer binding level.
  Possible values are - `logAndContinue`, `logAndFail` or `sendToDlq`
  +
  Default: `logAndFail`
  
  
negative.code: }
  ```
  
  and you only want to enable DLQ on the first input binding and skipAndContinue on the second binding, then you can do so on the consumer as below.
  
  `spring.cloud.stream.kafka.streams.bindings.process-in-0.consumer.deserializationExceptionHandler: sendToDlq`
  `spring.cloud.stream.kafka.streams.bindings.process-in-1.consumer.deserializationExceptionHandler: skipAndContinue`
  
  Setting deserialization exception handlers this way has a higher precedence than setting at the binder level.
  
  