Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
-
None
-
Important
Description
I think we're missing some API is missing to make this all usable.
A Topology/TStream domain user needs an easy way to get the PeriodicMXBean for a particular Topology.poll() invocation.
The PeriodicSource oplet implements PeriodicMXBean which allows changing the period.
The only demonstrated use is by DirectJobTest.jobPeriodicSourceCancellation(), which iterates over the Topology's underlying graph for instanceof PeriodicSource oplet (it's the only ProcessSource oplet in the graph for this test).
That's certainly not easy / convenient / nor in the "TStream" domain the user is mostly operating in.
djd vdogaru what schemes for addressing this have already been considered / decided? Some sort of "control bean registry service" where a user gets to supply a name (e.g., to poll()) and the runtime registers the bean (e.g., PeriodicMXBean) under that name? If there's not a concrete plan lets work on that here.