[
https://issues.apache.org/jira/browse/KAFKA-16863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17852793#comment-17852793
]
Muralidhar Basani commented on KAFKA-16863:
-------------------------------------------
Do we need a kip for this config cleanup ?
>From the description I understand we deprecate the below and create two new
>configs without prefix 'default.'
- default.deserialization.exception.handler
- default.production.exception.handler
Is it ok, if I work on this ? If it needs a kip, I can create one.
> Consider removing `default.` prefix for exception handler config
> ----------------------------------------------------------------
>
> Key: KAFKA-16863
> URL: https://issues.apache.org/jira/browse/KAFKA-16863
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: Matthias J. Sax
> Priority: Trivial
> Labels: need-kip
>
> Kafka Streams has a set of configs with `default.` prefix. The intent for the
> default-prefix is to make a distinction between, well the default, and
> in-place overwrites in the code. Eg, users can specify ts-extractors on a
> per-topic basis.
> However, for the deserialization- and production-exception handlers, no such
> overwrites are possible, and thus, `default.` does not really make sense,
> because there is just one handler overall. Via KIP-1033 we added a new
> processing-exception handler w/o a default-prefix, too.
> Thus, we should consider to deprecate the two existing configs names and add
> them back w/o the `default.` prefix.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
