Chaining query match streaming when one query is an input to another query on the same node requires emitting watermark upon creating complex events. I ain't touching it for now.
The (temporary) solution is to add a forwarding rule for such a node to send the matches of the one query to itself. This is a way faster fix (adding one line to config) and doesn't mess with watermarking in the flink system. For now, watermarks are emitted in one place only: in the source function upon receiving an event via tcp.
Related to #20
Chaining query match streaming when one query is an input to another query on the same node requires emitting watermark upon creating complex events. I ain't touching it for now.
The (temporary) solution is to add a forwarding rule for such a node to send the matches of the one query to itself. This is a way faster fix (adding one line to config) and doesn't mess with watermarking in the flink system. For now, watermarks are emitted in one place only: in the source function upon receiving an event via tcp.