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

["Robert Joseph Evans (JIRA)" <ji...@apache.org>]

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

Robert Joseph Evans resolved STORM-566.
---------------------------------------
       Resolution: Fixed
    Fix Version/s: 0.11.0

I pulled https://github.com/apache/storm/pull/817 into master.

[~jmartell7],

Thanks for the contribution.  I think I got the correct Joshua Martell, but if you didn't do that pull I will reassign the JIRA accordingly.

> 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
>            Assignee: Joshua Martell
>             Fix For: 0.11.0
>
>
> 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)