[
https://issues.apache.org/jira/browse/FLINK-14942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17191481#comment-17191481
]
Zhu Zhu commented on FLINK-14942:
---------------------------------
Hi [~sjwiesman][~qinjunjerry], just to confirm whether we need to wait for this
improvement before creating releasing 1.11.2 RC1?
I'm asking this because the deadline is later today, and this item is an
improvement.
> 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
> Affects Versions: 1.11.0
> Reporter: Jun Qin
> Assignee: Jun Qin
> Priority: Blocker
> Labels: pull-request-available, usability
> Fix For: 1.12.0, 1.11.2
>
>
> 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)
