[
https://issues.apache.org/jira/browse/SAMZA-554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14324995#comment-14324995
]
Yan Fang commented on SAMZA-554:
--------------------------------
Thanks, [~criccomini]. Since the Java Serde accepts type parameter, not sure if
I did it correctly. Could you just have a look at it?
https://reviews.apache.org/r/30920/diff/2-3/
> Simplify serde configuration by providing default serde names
> -------------------------------------------------------------
>
> Key: SAMZA-554
> URL: https://issues.apache.org/jira/browse/SAMZA-554
> Project: Samza
> Issue Type: Improvement
> Components: container
> Affects Versions: 0.8.0
> Reporter: Yan Fang
> Assignee: Yan Fang
> Priority: Minor
> Fix For: 0.9.0
>
> Attachments: SAMZA-554.2.patch, SAMZA-554.3.patch, SAMZA-554.patch
>
>
> Currently we provide StringSerde, JsonSerde, IntegerSerde, etc out of box. In
> order to use them, we always need to set,
> {code}
> serializers.registry.json.class=org.apache.samza.serializers.JsonSerdeFactory
>
> serializers.registry.string.class=org.apache.samza.serializers.StringSerdeFactory
>
> serializers.registry.integer.class=org.apache.samza.serializers.IntegerSerdeFactory
> {code}
> then we can use the serde name "json"
> {code}
> systems.kafka.samza.msg.serde=json
> {code}
> I think it will be more convenient if the system looks for these default
> serde names (such as "string", "json", "integer", etc). Then users do not
> need to worry about putting these out-of-box serde factories in the
> "registry" part which is kinda error-prone.
> Of course, it still allows users to override the serde name if they want and
> throws exceptions when it can not find the serde factory.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
