[jira] [Commented] (KAFKA-9559) Change the default "default serde" from ByteArraySerde to null

["Matthias J. Sax (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KAFKA-9559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17310090#comment-17310090 ] 

Matthias J. Sax commented on KAFKA-9559:
----------------------------------------

[~lct45] – I think we should also add corresponding checks to get clean error messages when we try to fall-back to the default serdes – atm, we know they can never be `null` but with this change they could be `null` and me might crash with a NPE what is bad user experience. Instead, we should check for the `null` condition and throw an informative `StreamsException` (or some sub-type).

> 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
>             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.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)