[
https://issues.apache.org/jira/browse/FLINK-24532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17443633#comment-17443633
]
lincoln lee commented on FLINK-24532:
-------------------------------------
[~twalthr] Could you give a specific case for this issue？I checked the
ChangelogNormalize implementation, it produces a +D row when input is
-U or +D, so I can't get your problem, a specific case may helps.
> Invalid deletions for time-versioned join with ChangelogNormalize
> -----------------------------------------------------------------
>
> Key: FLINK-24532
> URL: https://issues.apache.org/jira/browse/FLINK-24532
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / Planner, Table SQL / Runtime
> Reporter: Timo Walther
> Priority: Critical
>
> ChangelogNormalize replaces a +D row with a -U row derived from the previous
> inserted row. This means that the rowtime column is reset to the insertion
> time. In this case, a downstream time-versioned join produces an invalid
> result as a deletion is applied immediately instead of the original deletion
> timestamp.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
