[
https://issues.apache.org/jira/browse/KAFKA-16863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-16863:
------------------------------------
Description:
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.
KIP-1056:
[https://cwiki.apache.org/confluence/display/KAFKA/KIP-1056%3A+Remove+%60default.%60+prefix+for+exception+handler+StreamsConfig]
was:
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.
> 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
> Assignee: Muralidhar Basani
> Priority: Trivial
> Labels: 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.
> KIP-1056:
> [https://cwiki.apache.org/confluence/display/KAFKA/KIP-1056%3A+Remove+%60default.%60+prefix+for+exception+handler+StreamsConfig]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
