You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Timo Walther (Jira)" <ji...@apache.org> on 2021/10/13 12:21:00 UTC

[jira] [Updated] (FLINK-24532) Invalid deletions for time-versioned join with ChangelogNormalize

     [ https://issues.apache.org/jira/browse/FLINK-24532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timo Walther updated FLINK-24532:
---------------------------------
    Description: 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.  (was: 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, time-version joins produce an invalid result as a deletion is applied immediately instead of the original deletion timestamp.)

> 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.3.4#803005)