You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Matthias J. Sax (Jira)" <ji...@apache.org> on 2020/02/15 07:47:00 UTC

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

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

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

[~high.lee] Just to clarify – this ticket implies a backward incompatible change, and thus we cannot do it before 3.0 release. There is no timeline for a 3.0 major version bump atm – hence, we cannot really work on this ticket atm.

> 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: Sophie Blee-Goldman
>            Assignee: highluck
>            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)