You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Yaroslav Tkachenko (Jira)" <ji...@apache.org> on 2022/05/04 17:47:00 UTC

[jira] [Updated] (FLINK-25205) Optimize SinkUpsertMaterializer

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

Yaroslav Tkachenko updated FLINK-25205:
---------------------------------------
    Attachment: without-SinkUpsertMaterializer.png
                with-SinkUpsertMaterializer.png

> Optimize SinkUpsertMaterializer
> -------------------------------
>
>                 Key: FLINK-25205
>                 URL: https://issues.apache.org/jira/browse/FLINK-25205
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table SQL / Runtime
>            Reporter: Jingsong Lee
>            Priority: Major
>         Attachments: with-SinkUpsertMaterializer.png, without-SinkUpsertMaterializer.png
>
>
> SinkUpsertMaterializer maintains incoming records in state corresponding to the upsert keys and generates an upsert view for the downstream operator.
> It is intended to solve the messy order problem caused by the upstream computation, but it stores the data in the state, which will get bigger and bigger.
> If we can think that the disorder only occurs within the checkpoint, we can consider cleaning up the state of each checkpoint, which can control the size of the state.
> We can consider adding an optimized config option first.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)