Not exactly reproduciable. I cannot reproduce the problem in a test
environment with the same setting. This is only reproducible in PRD. I
guess it has something to do with the state itself.
Where you added the debugging log ? In RocksDBListState#get() ?
>
I added the debug log in
*org.apache.fli
Hi,
IIUC, Conditions to reproduce it are:
1. Using RocksDBStateBackend with incremental strategy
2. Using ListState in the stateful operator
3. enabling TTL with cleanupInRocksdbCompactFilter
4. adding a field to make the job trigger schema evolution
Then the exception will be thrown, right?
As fo
