Re: Inconsistent behavior between different states with ListState.get().iterator().remove()

Thanks for the response, filed https://issues.apache.org/jira/browse/FLINK-18707 as a minor bug. — Ken > On Jul 24, 2020, at 2:03 AM, Aljoscha Krettek wrote: > > That is a very good observation! > > In an ideal world, I would say we disallo

Re: Inconsistent behavior between different states with ListState.get().iterator().remove()

That is a very good observation! In an ideal world, I would say we disallow #remove() because we cannot efficiently implement it for RocksDB and we should keep the behaviour consistent between the backends. Now that we already have the functionality for the heap-based backends I think we canno

Inconsistent behavior between different states with ListState.get().iterator().remove()

Hi devs, If you use the FsStateBackend (or MemoryStateBackend), and you have ListState, then you can get an iterator and remove() an entry, and it all works as expected. If you use the RocksDBStateBackend, the remove() call doesn’t throw an exception, but the ListState isn’t updated. Seems li