Hi Danny,
You are right, we have already considered the watermark lateness in this
case.
However our Interval Join Operator has some bug that will still produce
records later than watermark.
I've created a issue[1], we can discuss it in the jira issue.
[1] https://issues.apache.org/jira/browse/FL
For SQL, we always hold back the watermark when we emit the elements, for time
interval:
return Math.max(leftRelativeSize, rightRelativeSize) + allowedLateness;
For your case, the watermark would hold back for 1 hour, so the left join
records would not delay when it is used by subsequent operat
Hi Bob,
This is Flink user mailing list. Please send to this mailing list using
english.
If you want to use Chinese, you can send it to user...@flink.apache.org
元始(Bob Hu) <657390...@qq.com> 于2020年7月3日周五 下午3:29写道：
> 您好，我想请教一个问题：
> flink双流表 interval join后再做window group是不是有问题呢，有些left join关联不上的数据会被
