Hi - We came across some (to us) unexpected behaviour in the Python

CountTumblingWindowAssigner

recently - it is backed by a non-purging

CountTrigger

and therefore produces a memory leak unless one replaces the trigger by a purging one using

.trigger()

. Are we missing something? Is there a usecase where one can use

CountTumblingWindowAssigner

with its current default trigger? I feel the default should be FIRE_AND_PURGE here, but wanted to ask before I file a JIRA.

@Urs Schoenenberger I guess you are right. Filed https://issues.apache.org/jira/browse/FLINK-31949 to track this issue. Would you like to contribute and fix this issue?