You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Yasuhiro Matsuda (JIRA)" <ji...@apache.org> on 2016/01/27 00:22:39 UTC

[jira] [Created] (KAFKA-3153) Serializer/Deserializer Registration and Type inference

Yasuhiro Matsuda created KAFKA-3153:
---------------------------------------

             Summary: 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.9.1.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)