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

Posted to issues@flink.apache.org by "Yun Gao (Jira)" <ji...@apache.org> on 2022/04/13 06:28:04 UTC

[jira] [Updated] (FLINK-19881) Optimize temporal join with upsert-Source(upsert-kafka)

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

Yun Gao updated FLINK-19881:
----------------------------
    Fix Version/s: 1.16.0

> Optimize temporal join with upsert-Source(upsert-kafka)
> -------------------------------------------------------
>
>                 Key: FLINK-19881
>                 URL: https://issues.apache.org/jira/browse/FLINK-19881
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table SQL / Runtime
>            Reporter: Leonard Xu
>            Priority: Minor
>              Labels: auto-deprioritized-major
>             Fix For: 1.15.0, 1.16.0
>
>
> Currently upsert-kafka will do normalize in a physical node named `ChangelogNormalize`, the normalization will do a deduplicate using state and produce `UPDATE_AFTER`, `DELETE` changelog. We do same thing In the state of temporal join operator,  we can merge them to one as an optimization  if the query contains temporal join an upsert-kafka.
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)