[
https://issues.apache.org/jira/browse/KAFKA-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15201131#comment-15201131
]
Michael Noll commented on KAFKA-3153:
-------------------------------------
[~guozhang], [~yasuhiro.matsuda]: What about this ticket? Was this still
referring to the our previous evaluation of the two different approaches of
serialization? If so, then I think this ticket is not needed anymore.
> 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)
