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/05 03:53:26 UTC

[jira] [Updated] (STORM-566) Unexpected trident spout metadata serialization

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

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

> Unexpected trident spout metadata serialization
> -----------------------------------------------
>
>                 Key: STORM-566
>                 URL: https://issues.apache.org/jira/browse/STORM-566
>             Project: Apache Storm
>          Issue Type: Bug
>          Components: storm-core
>            Reporter: Daniel Schonfeld
>
> ITridentSpout claims the metadata will be serialized utilizing the component's configuration Kryo serializers.
> Evidently (storm.trident.topology.state.TransactionalState) the way its serialized is with simple JSON and horribly calling toString() on a simple object.
> Either change the documentation or change the implementation.  It's currently misleading and also causing unrecoverable situations



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