[
https://issues.apache.org/jira/browse/STORM-468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14377164#comment-14377164
]
ASF GitHub Bot commented on STORM-468:
--------------------------------------
GitHub user jangie opened a pull request:
https://github.com/apache/storm/pull/477
[STORM-468] First attempt
Am pretty sure this is not the best way. Am open to suggestions.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jangie/storm STORM-468
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/storm/pull/477.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 #477
----
commit f910e0db9447ca0bdc1a382c09ee1a242f4fc166
Author: Jang-Soo Lee <[email protected]>
Date: 2015-03-24T02:34:59Z
Attempt at STORM-468
Am pretty sure this is not the best way. Am open to suggestions.
----
> java.io.NotSerializableException should be explained
> ----------------------------------------------------
>
> Key: STORM-468
> URL: https://issues.apache.org/jira/browse/STORM-468
> Project: Apache Storm
> Issue Type: Bug
> Affects Versions: 0.9.2-incubating
> Environment: Any
> Reporter: Jason Kania
> Priority: Minor
> Labels: newbie
>
> The occurrence of the NotSerializableException and how to avoid it should be
> better documented and the error from the code should be expanded to include
> some human readable message because it took a lot of searching to find out
> that the spouts and bolts need to create their variables in the prepare
> method in order to avoid this problem.
> The error text output could state that this is how to solve the problem.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
