Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/2433
@danny0405
Sorry I should explain the motivation before. The motivation is well
explained to the description on
https://issues.apache.org/jira/browse/STORM-2448.
Explaining background as far as I know, some vendors which leverages Storm
(via product, or cluster) are always struggling with ensuring users to upgrade
their clusters (or topologies) smoothly. It should be ideal if all users are
using most recent version of Storm, but it is sadly true that someone still
even uses Storm 0.10.x in their production.
The team which makes one of Storm's biggest contribution is also struggling
on this. They have put noticeable efforts to RAS in Storm 2.0.0 which really
helps utilizing huge cluster (I guess it is centralized), but it is even not
easy for them to persuade their all of clients to upgrade their topologies.
(I'm not quite sure it is similar case for them but you may understand the case
if you are working on company which number of employees goes over 1000~.)
STORM-2448 comes in as a workaround for addressing above issue. We should
(must, I wish) drop supporting them from Storm 3.0.0, but we may need to live
with this for now.
---
