[
https://issues.apache.org/jira/browse/KAFKA-9559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-9559:
-----------------------------------
Description:
The current default "default serde" is not particularly useful, and in almost
all cases is intended to be overwritten either by setting the config explicitly
or by specifying serdes directly in the topology. If a user does not set the
config and misses specifying a serde they will get a runtime ClassCastException
once they start processing unless they are in fact processing only bytes.
We should change the default default to null, so that an exception will instead
be thrown immediately on startup if a user failed to specify a serde somewhere
in their topology and it falls back to the unset default.
KIP-741:
[https://cwiki.apache.org/confluence/display/KAFKA/KIP-741%3A+Change+default+serde+to+be+null]
was:
The current default "default serde" is not particularly useful, and in almost
all cases is intended to be overwritten either by setting the config explicitly
or by specifying serdes directly in the topology. If a user does not set the
config and misses specifying a serde they will get a runtime ClassCastException
once they start processing unless they are in fact processing only bytes.
We should change the default default to null, so that an exception will instead
be thrown immediately on startup if a user failed to specify a serde somewhere
in their topology and it falls back to the unset default.
> Change the default "default serde" from ByteArraySerde to null
> --------------------------------------------------------------
>
> Key: KAFKA-9559
> URL: https://issues.apache.org/jira/browse/KAFKA-9559
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: A. Sophie Blee-Goldman
> Assignee: Leah Thomas
> Priority: Blocker
> Labels: kip
> Fix For: 3.0.0
>
>
> The current default "default serde" is not particularly useful, and in almost
> all cases is intended to be overwritten either by setting the config
> explicitly or by specifying serdes directly in the topology. If a user does
> not set the config and misses specifying a serde they will get a runtime
> ClassCastException once they start processing unless they are in fact
> processing only bytes.
> We should change the default default to null, so that an exception will
> instead be thrown immediately on startup if a user failed to specify a serde
> somewhere in their topology and it falls back to the unset default.
> KIP-741:
> [https://cwiki.apache.org/confluence/display/KAFKA/KIP-741%3A+Change+default+serde+to+be+null]
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
