Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/5337
I am not deeply into the Kinesis Consumer logic, just writing here to
double check that we do not build a solution where state grows infinitely.
For example, it would not be feasible to hold onto all shard info forever
(state would always grow), but there would need to be a way track all closed
shards via constant state (like a threshold timestamp, sequence number, etc).---
