You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "Robert Joseph Evans (JIRA)" <ji...@apache.org> on 2015/04/03 16:48:53 UTC
[jira] [Created] (STORM-750) Set Serialization Id for Config
Robert Joseph Evans created STORM-750:
-----------------------------------------
Summary: Set Serialization Id for Config
Key: STORM-750
URL: https://issues.apache.org/jira/browse/STORM-750
Project: Apache Storm
Issue Type: Bug
Reporter: Robert Joseph Evans
We have had several customers write bolts or spouts that don't do the right thing and end up caching the Config somewhere in the bolt or spout instance. Sometimes in odd ways through anonymous inner classes that should have been static but were not and debugging them because of the bad java serialization errors is really hard.
Instead of beating on them to clean up these references every time we upgrade a cluster, or force them to keep their client perfectly in sync with the server, I propose that we set the serialization id for Config. Config stores no state except in the parent class so it really should not matter if we add more methods to it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)