Hi Congxian,
Thanks but by doing that, we will lose some features like output of the late
data.
Original Message
Sender: Congxian Qiu
Recipient: Lasse Nedergaard
Cc: 廖嘉逸; u...@flink.apache.org;
dev@flink.apache.org
Date: Monday, Sep 23, 2019 19:56
Subject: Re: Per Key Grained Watermark
Hi
There was a discussion about this issue[1], as the previous discussion said
at the moment this is not supported out of the box by Flink, I think you
can try keyed process function as Lasse said.
[1]
http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Watermark-for-each-key-td274
Hi Jiayi
We have face the same challenge as we deal with IoT unit and they do not
necessarily share the same timestamp. Watermark or. Key would be perfect match
here. We tried to workaround with handle late events as special case with
sideoutputs but isn’t the perfect solution.
My conclusion i
Hi all,
Currently Watermark can only be supported on task’s level(or partition level),
which means that the data belonging to the faster key has to share the same
watermark with the data belonging to the slower key in the same key group of a
KeyedStream. This will lead to two problems:
1. L
