It sounds like it could be something worth addressing. I don't really know
the cost of this behavior. The pipeline is pretty easy to read. The
pipeline itself does not explicitly manage any state, so it would be in the
Flink execution of the GroupByKey primitive transform. The relevant code is
I think the author of this test is long gone, but the code originated
inside google. This query is not part of the original Nexmark suite but was
designed to exercise corner cases caused by out of order events, so that is
what you are probably seeing. Here are relevant bits from the original
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
