A separate server to accept control messages from the coordinator.
Functionality:
both incoming and outcoming communication (receiving instructions and reporting available to commit)
report healthy on the request for a switch (how to monitor for overload on the flink engine?)
trigger buffering events of the partitioning input from t_0 until t_1 (separate data stream, same sink but triggered on demand?)
flush the buffer to a new target
Implementation
[x] Send control message just like any other event. Create a super class from which AtomicEvent would inherit that would have a field with a type of a message (control or regular)
[x] filter the inputEventStream to branch it into the regular event stream and control stream based on the message type
[ ] Apply Windowing based on t_0 and t_1?
[ ] Define custom trigger?
[ ] Reuse the SocketSink
[ ] Define a custom time trigger for the event stream on t_1
[ ] Override clear() method to clear state (all partial matches) on the trigger from (6) from the event stream on t_1
Kristina-Pianykh
commented
4 months ago
A separate server to accept control messages from the coordinator.
Functionality:
Implementation
AtomicEventwould inherit that would have a field with a type of a message (control or regular)inputEventStreamto branch it into the regular event stream and control stream based on the message typeSocketSinkclear()method to clear state (all partial matches) on the trigger from (6) from the event stream on t_1