...

1. Deprecate the below two configs in org.apache.kafka.streams.StreamsConfig
   1. default.deserialization.exception.handler
   2. default.production.exception.handler
   3. and deprecate DEFAULT_DESERIALIZATION_EXCEPTION_HANDLER_CLASS_DOC
2. Configs to be added to org.apache.kafka.streams.StreamsConfig
   1. deserialization.exception.handler
   2. production.exception.handler
   3. and add DESERIALIZATION_EXCEPTION_HANDLER_CLASS_DOC
3. Update all the relevant dependency classes, so that both old and new configs are supported
   1. Update ConfigDef in TopologyConfig and code blocks like isTopologyOverride(DEFAULT_DESERIALIZATION_EXCEPTION_HANDLER_CLASS_CONFIG, topologyOverrides)) with new configs, so that code behaves the same for both the old and new configs
   2. RecordDeserializer update handleDeserializationFailure method
4. Mark the tests depending on old configs as deprecated and introduce new tests in the below
   1. InternalTopologyBuilderTest
   2. StreamTaskTest
   3. StreamThreadTest
5. If user sets both old and new configs, a ConfigException to be thrownnew config should be considered. And always look for new config, and if it's not available, fallback to old one.

Compatibility, Deprecation, and Migration Plan

...

But if user sets both old and new configs, a ConfigException to be thrownlike in other patterns, new config should be considered. And always look for new config, and if it's not available, fallback to old one.

Test Plan

Describe in few sentences how the KIP will be tested. We are mostly interested in system tests (since unit-tests are specific to implementation details). How will we know that the implementation works as expected? How will we know nothing broke?

...