Operator ControlNotificationSource
The ControlNotificationSource operator provides a connector between control events and data streams by turning control notifications into tuples. It generates a stream of tuples that are derived from notifications from MBeans in the JobControlPlane. A tuple is generated when a notification is issued by any MBean in the JobControlPlane whose object name is listed in objectNames. The notifications must pass the filters that are defined by the filters parameter. Any value set in filters is a filter on the prefix of the notification type. A notification results in a tuple if its type starts with at least one of the type prefixes set in filters. If filters is not set, then every notification results in a tuple.The ControlNotificationSource is useful for existing operators that have control ports.For example, control actions can drive the set of keys in a DynamicFilter operator by submittingthe tuples that are derived from notifications to the input ports that modify the set of keys in the operator.
Summary
- Ports
- This operator has 0 input ports and 1 output port.
- Windowing
- This operator does not accept any windowing configurations.
- Parameters
- This operator supports 2 parameters.
Required: objectNames
Optional: filters
- Metrics
- This operator does not report any metrics.
Properties
- Implementation
- Java
- Assignments
- Java operators do not support output assignments.
- Ports (0)
-
- Properties
-
- Optional: false
Required: objectNames
Optional: filters
- filters
-
Specifies a set of notification type filters. Any notification from an MBean with a type prefix in the set of filters is submitted as a tuple. When not set, all notifications are submitted as tuples.
- objectNames
-
Specifies the object names of MBeans to listen to notifications from.
- Operator class library