Github user je-ik commented on the issue:
https://github.com/apache/flink/pull/5185
@StefanRRichter I think that was exactly the initial idea, but then we came
into troubles with the savepoints and changing list type. Also as @aljoscha
mentioned, it can be confusing for users to see `
Github user StefanRRichter commented on the issue:
https://github.com/apache/flink/pull/5185
Just a thought, how about having all this implemented on top of a map
state, and also include the current size as a special entry in the map (with
the size field having a key that makes it lex
Github user je-ik commented on the issue:
https://github.com/apache/flink/pull/5185
@StephanEwen I think it should be configurable. As Aljoscha pointed out, it
is needed to ensure that these two representations have the same serialized
form in checkpoints, because that way users can s
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/5185
Is the general thought to always have list state as a map, or only fallback
to that way if the lists cross a certain threshold?
Since list state backs many common operations (non aggregat
Github user aljoscha commented on the issue:
https://github.com/apache/flink/pull/5185
It doesn't have to be the same while were working on it in RocksDB but when
checkpointing it should be written in the same format. This might be trickier
than it sounds, btw, but I don't think we ca
Github user je-ik commented on the issue:
https://github.com/apache/flink/pull/5185
@aljoscha I updated the title. I'm a little concerned about the
serialization in savepoint. If the serialization is *exactly* the same, doesn't
that actually mean that again, the whole List will be sto
