Hi Muhammad, With "not going done" you mean that it's still growing or that it's constant? In case of it being constant, that's pretty much what is expected, right? If it's still growing, the only reason I could come up with: Do you work in event time and have watermarks properly assigned with a boundedTimestampExtractor or ascendingTimestampExtractor?
Best regards Theo Von: "Muhammad Hakim" <muhammad.ha...@gojek.com> An: "user" <user@flink.apache.org> Gesendet: Dienstag, 1. Oktober 2019 09:08:22 Betreff: CEP operator in SQL pattern match does not clear it's state Hi All, We've been experimenting with `MATCH_RECOGNIZE` clause on Flink 1.8. We tried to have a pattern match within one hour. According to [ https://ci.apache.org/projects/flink/flink-docs-stable/dev/table/streaming/match_recognize.html#time-constraint | https://ci.apache.org/projects/flink/flink-docs-stable/dev/table/streaming/match_recognize.html#time-constraint ] , using `WITHIN` will control the memory usage. We've been running queries using CEP for almost one week and memory usage is not going down. Are we missing something?
