You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "Parth Brahmbhatt (JIRA)" <ji...@apache.org> on 2015/04/07 21:10:12 UTC

[jira] [Commented] (STORM-760) use JSON for conf serialization

    [ https://issues.apache.org/jira/browse/STORM-760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14483831#comment-14483831 ] 

Parth Brahmbhatt commented on STORM-760:
----------------------------------------

There is one place else which is backtype.storm.utils.LocalState which currently writes the state to localdisk and uses java serialization. It is ok because it writes java's hashtable so I haven't seen it causing any issues but it might be better to convert that into Json as well.

> use JSON for conf serialization
> -------------------------------
>
>                 Key: STORM-760
>                 URL: https://issues.apache.org/jira/browse/STORM-760
>             Project: Apache Storm
>          Issue Type: Bug
>            Reporter: Robert Joseph Evans
>            Assignee: Robert Joseph Evans
>
> Now that STORM-634 has gone in, the only real place we still use java serialization that is not required by the contract with the end user is when nimbus writes out the topology conf, and the worker/supervisor tries to read it back in.  We already write it out using JSON when submitting a topology, we should do the same here to avoid rolling upgrade issues, ideally compressed to save space too.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)