...

1. Deprecate the below two configs in org.apache.kafka.streams.StreamsConfig
   1. default.deserialization.exception.handler
   2. default.production.exception.handler
2. Configs to be added to org.apache.kafka.streams.StreamsConfig
   1. deserialization.exception.handler
   2. production.exception.handler
3. Rename the below template configs
   1. DEFAULT_DESERIALIZATION_EXCEPTION_HANDLER_CLASS_DOC to DESERIALIZATION_EXCEPTION_HANDLER_CLASS_DOC
   2. DEFAULT_PRODUCTION_EXCEPTION_HANDLER_CLASS_DOC to PRODUCTION_EXCEPTION_HANDLER_CLASS_DOC
4. 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
5. Mark the tests depending on old configs as deprecated and introduce new tests in the below
   1. InternalTopologyBuilderTest
   2. StreamTaskTest
   3. StreamThreadTest
6. If user sets both old and new configs, a ConfigException to be thrown.

Compatibility, Deprecation, and Migration Plan

...

Basically we have to make sure that after deprecation, the functionality for StreamsConfig, TopologyConfig and RecordDeserializer remains the same and should behave exactly same for old and new configs.

But if user sets both old and new configs, a ConfigException to be thrown.

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?

...