[jira] [Updated] (STORM-750) Set Serialization Id for Config

["P. Taylor Goetz (JIRA)" <ji...@apache.org>]

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

P. Taylor Goetz updated STORM-750:
----------------------------------
    Fix Version/s:     (was: 0.11.0)
                   0.10.0

> 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
>            Assignee: Robert Joseph Evans
>              Labels: newbie
>             Fix For: 0.10.0
>
>
> 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)