Hi, We are working on a Flink project and enhancing some state backend functionality. We are using NEXMark benchmark to compare different state backends performance of Flink. While running NEXMark queries using Flink runner of Beam we have noticed that there is quite a lot of non-existent read from the state-backed.
For example, when running query 11 with RocksDB state-backed, we had around 368 successful reads while we had around 527 attempts to read non-existent reads. We are curious if that is intentional and if so what's the rationale behind it? -- Regards, Sruthi
