sparse should be able to deploy topology in deactivated state, since best practices guideline to update Storm in production recommends using new second cluster and deploying topologies deactivated.
I suggest adding new option to sparse submit ... -i (inactive) or even allow passing Submit Options to thrift in some way.
It should be fairly easy to implement as Thrift has "submitTopologyWithOpts" method (instead of plain submitTopology). You can pass Submit options there as last arg.
sparse should be able to deploy topology in deactivated state, since best practices guideline to update Storm in production recommends using new second cluster and deploying topologies deactivated.
I suggest adding new option to
sparse submit ... -i(inactive) or even allow passing Submit Options to thrift in some way.It should be fairly easy to implement as Thrift has "submitTopologyWithOpts" method (instead of plain submitTopology). You can pass Submit options there as last arg.
see: https://mail-archives.apache.org/mod_mbox/storm-user/201504.mbox/D1489B2C.1E73A%25ssingh2@walmartlabs.com
submitOptions.set_initial_status(TopologyInitialStatus.INACTIVE)