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 2016/01/04 23:09:40 UTC
[jira] [Resolved] (STORM-1412) Null check should be done in the
first place
[ https://issues.apache.org/jira/browse/STORM-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Joseph Evans resolved STORM-1412.
----------------------------------------
Resolution: Fixed
Fix Version/s: 0.11.0
Thanks [~vesense],
I merged this into master.
> Null check should be done in the first place
> --------------------------------------------
>
> Key: STORM-1412
> URL: https://issues.apache.org/jira/browse/STORM-1412
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-core
> Reporter: Xin Wang
> Assignee: Xin Wang
> Fix For: 0.11.0
>
>
> Null check should be done in the first place for class User, otherwise it may cause NullPointerException.
> before fix:
> {code}
> private void moveTopology(TopologyDetails topo, Set<TopologyDetails> src, String srcName, Set<TopologyDetails> dest, String destName) {
> LOG.debug("For User {} Moving topo {} from {} to {}", this.userId, topo.getName(), srcName, destName);
> if (topo == null) {
> return;
> }
> {code}
> after fix:
> {code}
> private void moveTopology(TopologyDetails topo, Set<TopologyDetails> src, String srcName, Set<TopologyDetails> dest, String destName) {
> if (topo == null) {
> return;
> }
> LOG.debug("For User {} Moving topo {} from {} to {}", this.userId, topo.getName(), srcName, destName);
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)