You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "anugrah (JIRA)" <ji...@apache.org> on 2017/05/19 14:02:04 UTC
[jira] [Assigned] (KAFKA-5245) KStream builder should capture
serdes
[ https://issues.apache.org/jira/browse/KAFKA-5245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
anugrah reassigned KAFKA-5245:
------------------------------
Assignee: anugrah
> 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.3.15#6346)