You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Robert Metzger (Jira)" <ji...@apache.org> on 2020/11/02 06:10:00 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 ]
Robert Metzger updated FLINK-19881:
-----------------------------------
Component/s: Table SQL / Runtime
> Optimize temporal join with upsert-Source(upsert-kafka)
> -------------------------------------------------------
>
> Key: FLINK-19881
> URL: https://issues.apache.org/jira/browse/FLINK-19881
> Project: Flink
> Issue Type: Sub-task
> Components: Table SQL / Runtime
> Reporter: Leonard Xu
> Priority: Major
>
> 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.3.4#803005)