Github user StefanRRichter commented on the issue:
https://github.com/apache/flink/pull/6186
@sihuazhou I think your concern and suggestion can clearly make sense for
some cases. However I don't think it should be a general default as well
because I can also find cases where this is not what a user might want. For
example, TTL could be used for compliance with some user data privacy law. In
this case, the law does not care about technical details like restores but only
about wall-clock time, e.g. from the last user interaction.
As this is a new feature, there is also no regression and users can still
go for a custom timer-based solution as alternative. I agree for some cases it
makes sense to have this timeshift and also your outlined approach can make
sense. However, I think this does not have to block this PR, because I would
consider it a feature/improvement on top of this work. We could still target to
have your suggested followup before the release.
---
