[
https://issues.apache.org/jira/browse/STORM-760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14483850#comment-14483850
]
ASF GitHub Bot commented on STORM-760:
--------------------------------------
GitHub user revans2 opened a pull request:
https://github.com/apache/storm/pull/513
STORM-760: Use JSON for serialized conf
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/revans2/incubator-storm STORM-760
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/storm/pull/513.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 #513
----
commit 99aaaae2734281d483a50a2adbc4b43111621abf
Author: Robert (Bobby) Evans <[email protected]>
Date: 2015-04-07T19:15:09Z
STORM-760: Use JSON for serialized conf
----
> 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)
