My use case is that I'm producing a set of measurements by key every 60 seconds. Currently, this is handled with the usual pattern of keyBy().window(Tumbling...(60)).process(...) I need to provide the same output, but as a result of a timeout. The data needed for the timeout summary will be in the global state for that key. This seems possible by either using the timer service in the process function without a window (e.g. keyBy(..).process(..)) or by using a customer trigger. Why choose one or the other?
-- Thanks, Aeden GitHub: https://github.com/aedenj Linked In: http://www.linkedin.com/in/aedenjameson
