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 2019/10/18 17:48:00 UTC

[jira] [Commented] (KAFKA-5245) KStream builder should capture serdes

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

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

[~bbejeck], [~guozhang] This ticket should be covered already. With the optimization layer we added, we do forward Serdes down streams if possible.

Or is the any other work left to resolve 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
>            Priority: Minor
>              Labels: needs-kip
>
> 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
(v8.3.4#803005)