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

Weijie Guo updated FLINK-25205:
-------------------------------
    Fix Version/s: 2.0.0
                       (was: 1.20.0)

> 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
>            Assignee: lincoln lee
>            Priority: Major
>             Fix For: 2.0.0
>
>         Attachments: flamegraph-final.html, 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.10#820010)

Reply via email to