flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Flink Jira Bot (Jira)" <j...@apache.org>
Subject [jira] [Updated] (FLINK-19881) Optimize temporal join with upsert-Source(upsert-kafka)
Date Sat, 22 May 2021 22:53:02 GMT

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

Flink Jira Bot updated FLINK-19881:
    Labels: stale-major  (was: )

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community
manage its development. I see this issues has been marked as Major but is unassigned and neither
itself nor its Sub-Tasks have been updated for 30 days. I have gone ahead and added a "stale-major"
to the issue". If this ticket is a Major, please either assign yourself or give an update.
Afterwards, please remove the label or in 7 days the issue will be deprioritized.

> 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: Major
>              Labels: stale-major
>             Fix For: 1.14.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

View raw message