I can’t understand the ‘queryTimeAfterNumEntries’ parameter of the ‘cleanupInRocksdbCompactFilter’ method regarding TTL settings in Apache Flink 1.15.
Doc says:

Cleanup expired state while Rocksdb compaction is running.
RocksDB compaction filter will query current timestamp, used to check expiration, from Flink every time after processing queryTimeAfterNumEntries number of state entries. Updating the timestamp more often can improve cleanup speed but it decreases compaction performance because it uses JNI call from native code.
Parameters:
queryTimeAfterNumEntries – number of state entries to process by compaction filter before updating current timestamp

When the compaction filter process state entries? How can I test the functioning of this cleanup strategy?