Hi Jin,
as you have figured out, if something goes wrong with watermarks it's
usually because of the watermark generator (sorry for not receiving any
feedback whatsoever).
Thank you very much for sharing your solution!
On Thu, Jun 3, 2021 at 8:51 PM Jin Yi wrote:
> just to resolve this thread,
just to resolve this thread, i figured out the issue. there's a local
version of a watermark strategy that we use when running locally for
development that didn't work correctly on many events with the same
timestamp which the fake data generation that happens for local runs has a
tendency to do.
(sorry that the last sentence fragment made it into my email... it was a
draft comment that i forgot to remove. my thoughts are/were complete in
the first message.)
i do have follow-up questions/thoughts for this thread though. given my
current setup, it seems it's more expected to have the beha
hello,
sorry for a long post, but this is a puzzling problem and i am enough of a
flink non-expert to be unsure what details are important or not.
background:
i have a flink pipeline that is a series of custom "joins" for the purposes
of user event "flattening" that i wrote a custom KeyedCoProces
