Hello, I found an SO thread that clarifies some details of window state size [1]. I would just like to confirm that this also applies when using a global window with a custom trigger.
The reason I ask is that the TriggerResult API is meant to cover all supported scenarios, so FIRE vs FIRE_AND_PURGE is relevant, for example, for a ProcessWindowFunction that holds all input records until it fires. However, I assume there would be no distinction if I use a (Rich)AggregateFunction, regardless of window type (global vs timed), but I'd like to be sure. Regards, Alexis. [1] https://stackoverflow.com/questions/55247668/flink-window-state-size-and-state-management
