Muhammad,
Can you give us bit more details on how this works. Topologies
supposed to be long running. I do see use for this, just
curious that users can automate a topology activate or
deactivate using UI api.
Thanks,
Harsha
On Tue, Jan 13, 2015, at 08:13 AM, Muhammad Ali A'råby wrote:
> Dear all,
> I am implementing a set of classes for scheduled topology works. For
> example when you want to disable/enable topologies periodically. This
> codes are having mechanisms for deciding whether a topology is finished
> working (are all tuples fully processed), mechanism for bolt to have an
> alternate prepare for every reboot of topology, etc.
> I am wondering where should I commit my code? Each class separately in
> storm-core package (e.g. ScheduledBolt in
> storm/storm-core/src/jvm/backtype/storm/bolt, ScheduledTopology in
> storm/storm-core/src/jvm/backtype/storm/topology, etc.) or all of them in
> a package somewhere?
> Sincerely,Muhammad-Ali A'rabi
