Hi All,
I was wondering if there is any way to get the time since the topology was
last updated?
It seems the submission time value returned by the tracker API
/topologies/executionstate does not change after an update (it is fixed for
the lifetime of the topology).
The instance uptimes could
implementation simpler
> > - state is deterministic across restarts
> > - makes it easy to reason and debug
> >
> > The hard limit is not a problem at all since most of the topologies will
> > be never that big.
> > If you can handle Twitter topologies cleanly,
Hi all,
A while ago I emailed about the issue of how fields (key) grouped routing
in Heron was not consistent across an update and how this makes preserving
state across an update very difficult and also makes it
difficult/impossible to analyse or predict tuple flows through a
current/proposed
