[
https://issues.apache.org/jira/browse/FLINK-25528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17494474#comment-17494474
]
刘方奇 commented on FLINK-25528:
-----------------------------
[~yunta] THX for your advice. But as I see, the incremental checkpoint is a
native snapshot actually. If "native snapshot" is the point, we can solve the
problem simply now as I explained above. What is the "full native checkpoint"
means? In my opinion, "full native checkpoint" is the incremental checkpoint
that I mentioned cause state-processor-api only checkpoint once.
PS: state-processor-api writer requires a backend option, we can simply support
any backend's snapshot strategy if we solve the problem that we can only use
the SAVEPOINT option.
The JIAR that you mentioned seems like Flink savePoint can support do the work
incrementally and natively in the future. Do you mean that we can use a better
way to improve state-processor-api?
If what I understand was wrong, just ping me. THX for your time.
> 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)
