This page is meant as a template for writing a KIP. To create a KIP choose Tools->Copy on this page and modify with your content and replace the heading with the next KIP number and a description of your issue. Replace anything in italics with your own description.

Status

Current state: "Under DiscussionAccepted"

Discussion thread: here 

JIRA: here 

...

Thus, we should consider to deprecate the two existing configs names and add them back w/o the `default.` prefix.

Public Interfaces

Target release 4.0

Changes to org.apache.kafka.streams.StreamsConfig

...

• deserialization.exception.handler
• production.exception.handler

      3. Adding new public method to get the new config for deserialization exception handler deserializationExceptionHandler()

      4. Adding new public method to get the new config for production exception handler productionExceptionHandler()

      5. Marking defaultDeserializationExceptionHandler() as deprecated

Proposed Changes

As such there are no functional changes at all. The main changes look like below.

...

Compatibility, Deprecation, and Migration Plan

The below configs in StreamsConfig will be marked for deprecation, and new configs will be introduced, and in later further releases, they could be removed

• default.deserialization.exception.handler
• default.production.exception.handler
• DEFAULT_DESERIALIZATION_EXCEPTION_HANDLER_CLASS_DOC

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.

...