[
https://issues.apache.org/jira/browse/KAFKA-5245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16048738#comment-16048738
]
Evgeny Veretennikov commented on KAFKA-5245:
--------------------------------------------
There are actually a lot of KStream methods, that require serdes again, not
only groupByKey(). For example, there are print(), through(), to(), etc. We
should pass serdes from builder.stream() to all such methods, am I right?
Also, behaviour of methods like groupByKey() will change after solving this
ticket. Clients could be broken, in case they really need to use default
serdes. Do we need KIP for this ticket?
> KStream builder should capture serdes
> --------------------------------------
>
> Key: KAFKA-5245
> URL: https://issues.apache.org/jira/browse/KAFKA-5245
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Affects Versions: 0.10.2.0, 0.10.2.1
> Reporter: Yeva Byzek
> Assignee: anugrah
> Priority: Minor
> Labels: beginner, newbie
>
> Even if one specifies a serdes in `builder.stream`, later a call to
> `groupByKey` may require the serdes again if it differs from the configured
> streams app serdes. The preferred behavior is that if no serdes is provided
> to `groupByKey`, it should use whatever was provided in `builder.stream` and
> not what was in the app.
> From the current docs:
> “When to set explicit serdes: Variants of groupByKey exist to override the
> configured default serdes of your application, which you must do if the key
> and/or value types of the resulting KGroupedStream do not match the
> configured default serdes.”
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
