[jira] [Commented] (FLINK-14942) State Processing API: add an option to make deep copy

["Congxian Qiu(klion26) (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-14942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17173767#comment-17173767 ] 

Congxian Qiu(klion26) commented on FLINK-14942:
-----------------------------------------------

After savepoint relocatable, I think we need to make a deep copy default for StateProcessing API now. because we assume that all the data and metadata are in the same directory.

> State Processing API: add an option to make deep copy
> -----------------------------------------------------
>
>                 Key: FLINK-14942
>                 URL: https://issues.apache.org/jira/browse/FLINK-14942
>             Project: Flink
>          Issue Type: Improvement
>          Components: API / State Processor
>            Reporter: Jun Qin
>            Assignee: Jun Qin
>            Priority: Major
>              Labels: usability
>             Fix For: 1.12.0
>
>
> Current when a new savepoint is created based on a source savepoint, then there are references in the new savepoint to the source savepoint. Here is the [State Processing API doc|https://ci.apache.org/projects/flink/flink-docs-release-1.9/dev/libs/state_processor_api.html] says: 
> bq. Note: When basing a new savepoint on existing state, the state processor api makes a shallow copy of the pointers to the existing operators. This means that both savepoints share state and one cannot be deleted without corrupting the other!
> This JIRA is to request an option to have a deep copy (instead of shallow copy) such that the new savepoint is self-contained. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)