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 Sun, 30 May 2021 23:14:01 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: auto-deprioritized-major  (was: stale-major)
    Priority: Minor  (was: Major)

This issue was labeled "stale-major" 7 ago and has not received any updates so it is being
deprioritized. If this ticket is actually Major, please raise the priority and ask a committer
to assign you the issue or revive the public discussion.


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

Mime
View raw message