You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Jingsong Lee (Jira)" <ji...@apache.org> on 2021/09/10 01:51:00 UTC
[jira] [Reopened] (FLINK-23054) Correct upsert optimization by
upsert keys
[ https://issues.apache.org/jira/browse/FLINK-23054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jingsong Lee reopened FLINK-23054:
----------------------------------
Re-open for 1.13
> Correct upsert optimization by upsert keys
> ------------------------------------------
>
> Key: FLINK-23054
> URL: https://issues.apache.org/jira/browse/FLINK-23054
> Project: Flink
> Issue Type: Sub-task
> Components: Table SQL / Runtime
> Reporter: Jingsong Lee
> Assignee: Jingsong Lee
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.14.0
>
>
> After FLINK-22901.
> We can use upsert keys to fix upsert join, upsert rank, and upsert sink.
> * For join and rank: if input has no upsert keys, do not use upsert optimization.
> * For upsert sink: if input has unique keys but no upsert keys, we need add a materialize operator to produce upsert records.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)