Github user aljoscha commented on the issue:
https://github.com/apache/flink/pull/5185
The concept of this looks good. However, if we want to merge it I think we
have to make this a standalone thing and not depend on other states because
this can have unforeseen consequences for future developments. I can think of
several cases where the current approach would lead to surprising problems:
- a user inspects a savepoint and finds a `MapState` and a `ValueState`
instead of the `ListState` they're expecting (becomes a problem when we have
tools for inspecting savepoints and also is problematic for compatibility of
the savepoint format between different state backends)
- (related to the above) the "binary format" of the savepoint is different
between the two list implementations. This leads to problems if you want to
change the implementation between restoring from a savepoint and when you want
to switch backends (which we currently don't support).
- if/when we have metrics for user states this would export metrics for a
`MapState` and a `ValueState` and not for one expected `ListState`
---
