You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "刘方奇 (Jira)" <ji...@apache.org> on 2022/01/05 09:07:00 UTC

[jira] [Updated] (FLINK-25528) state processor api do not support increment checkpoint

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

刘方奇 updated FLINK-25528:
------------------------
    Description: 
As the title, in the state-processor-api, we use the savepoint opition to snapshot state defaultly in org.apache.flink.state.api.output.SnapshotUtils.
But in many cases, we maybe need to snapshot state incremently which have better performance than savepoint.

Shall we add the config to chose the checkpoint way just like flink stream backend?

  was:
As the title, in the state-processor-api, we use the savepoint opition to snapshot stete defaultly in org.apache.flink.state.api.output.SnapshotUtils.
But in many cases, we maybe need to snapshot state incremently which have better performance than savepoint.

Shall we add the config to chose the checkpoint way just like flink stream backend?


> state processor api do not support increment checkpoint
> -------------------------------------------------------
>
>                 Key: FLINK-25528
>                 URL: https://issues.apache.org/jira/browse/FLINK-25528
>             Project: Flink
>          Issue Type: Improvement
>          Components: API / State Processor, Runtime / State Backends
>            Reporter: 刘方奇
>            Priority: Major
>
> As the title, in the state-processor-api, we use the savepoint opition to snapshot state defaultly in org.apache.flink.state.api.output.SnapshotUtils.
> But in many cases, we maybe need to snapshot state incremently which have better performance than savepoint.
> Shall we add the config to chose the checkpoint way just like flink stream backend?



--
This message was sent by Atlassian Jira
(v8.20.1#820001)