[
https://issues.apache.org/jira/browse/STORM-566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14973319#comment-14973319
]
ASF GitHub Bot commented on STORM-566:
--------------------------------------
GitHub user jmartell7 opened a pull request:
https://github.com/apache/storm/pull/817
Improve documentation including incorrect Kryo ser. framework docs
Improve documentation including incorrect serialization framework issue
described in STORM-566.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jmartell7/storm STORM-566-trident-spout-docs
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/storm/pull/817.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #817
----
commit ce90df5f7cb8ad35fdea2a39bf1c0f39f0b2eff5
Author: jmartell7 <[email protected]>
Date: 2015-10-25T15:58:48Z
Improve documentation including incorrect Kryo serialization framework doc
Improve documentation including incorrect serialization framework issue
described in STORM-566.
----
> 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)
