You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Guozhang Wang (JIRA)" <ji...@apache.org> on 2016/03/18 18:10:33 UTC
[jira] [Comment Edited] (KAFKA-3153) Serializer/Deserializer
Registration and Type inference
[ https://issues.apache.org/jira/browse/KAFKA-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15201799#comment-15201799 ]
Guozhang Wang edited comment on KAFKA-3153 at 3/18/16 5:10 PM:
---------------------------------------------------------------
Closing as "wont fix" for now.
was (Author: guozhang):
Closing now.
> Serializer/Deserializer Registration and Type inference
> -------------------------------------------------------
>
> Key: KAFKA-3153
> URL: https://issues.apache.org/jira/browse/KAFKA-3153
> Project: Kafka
> Issue Type: Sub-task
> Components: kafka streams
> Reporter: Yasuhiro Matsuda
> Assignee: Yasuhiro Matsuda
> Fix For: 0.10.0.0
>
>
> This changes the way serializer/deserializer are selected by the framework.
> The new scheme requires the app dev to register serializers/deserializers for types using API. The framework infers the type of data from topology and uses appropriate serializer/deserializer. This is best effort. Type inference is not always possible due to Java's type erasure. If a type cannot be determined, a user code can supply more information.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)