You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "Rick Kellogg (JIRA)" <ji...@apache.org> on 2015/10/09 02:35:28 UTC

[jira] [Updated] (STORM-168) Serialization of spouts/bolts

     [ https://issues.apache.org/jira/browse/STORM-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rick Kellogg updated STORM-168:
-------------------------------
    Component/s: storm-core

> Serialization of spouts/bolts
> -----------------------------
>
>                 Key: STORM-168
>                 URL: https://issues.apache.org/jira/browse/STORM-168
>             Project: Apache Storm
>          Issue Type: New Feature
>          Components: storm-core
>            Reporter: James Xu
>            Priority: Minor
>
> https://github.com/nathanmarz/storm/issues/367
> Once annoying thing about Java serialization is that it requires all serializable objects to be explicitly marked with Serializable interface. When using 3rd party libraries, sometimes people forget to do this. An idea here is to use Kryo serialization instead and have it default to Java serialization. The serializer should be prepped with the same serializers as is used for the Kryo serializer for tuples in the topology.
> ----------
> RomezzBorisov: It should be possible to choose the s11n approach via configuration
> ----------
> danehammer: @nathanmarz Can you explain further? Would this be implementing a spout serializer? A bolt serializer?
> ----------
> RomezzBorisov: It should be possible to provide a custom s11n for Storm objects in topology (bolts and spouts both, I don't think it's necessary to distinguish them) via implementing smth like StormSystemSerializer interface.
> The instance of serializer should be passed to topology builder.
> There should be several default implementations like JavaSystemSerializer, KryoSystemSerializer e.t.c.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)