The view A try to do de-duplication using event time, which will still
produce update rows. if you using proc time to do de-duplication.Then the
view A should only produce append only rows.
Best regards,
Yuxia
> 2022年10月15日 上午9:50，liebin...@whu.edu.cn 写道：
>
> I had a problem with Interva
Why keep the first row still produce update/delete rows?
There was a similar question before. Jark said that keep the first line should
produce an append-only stream and interval join can consume from it. The link
to this question is:
https://lists.apache.org/thread/z5w5n7o9g87dtb7p7q7p7vrvowqh
> view A should only produce insert rows
No, the view A will still produce update/delete rows.
Best regards,
Yuxia
> 2022年10月15日 上午9:50，liebin...@whu.edu.cn 写道：
>
> view A should only produce insert rows
I had a problem with Interval Join after using Deduplicate. I'm using Flink
version 1.15.
I want to use Flink's Interval Join for double-stream association, and my first
table needs to be de-duplicated. Here is my sample code.
```
CREATE TEMPORARY TABLE `source` (
id INT,
name STRING,
eve
