[
https://issues.apache.org/jira/browse/FLINK-22256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17340698#comment-17340698
]
Till Rohrmann edited comment on FLINK-22256 at 5/7/21, 9:39 AM:
----------------------------------------------------------------
cc [~pnowojski], [~joemoe] we are building quite some hacks into VVP to work
around this problem. I guess what we are looking for would be a stable API for
interacting with checkpoints and savepoints. API here mainly refers to the
metadata format.
was (Author: till.rohrmann):
cc [~pnowojski], [~joemoe] we are building quite some hacks into VVP to work
around this problem.
> Persist checkpoint type information
> -----------------------------------
>
> Key: FLINK-22256
> URL: https://issues.apache.org/jira/browse/FLINK-22256
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Checkpointing
> Reporter: Fabian Paul
> Priority: Major
>
> As a user, it is retrospectively difficult to determine what kind of
> checkpoint (i.e. incremental, unaligned, ...) was performed when looking only
> at the persisted checkpoint metadata.
> The only way would be to look into the execution configuration of the job
> which might not be available anymore and can be scattered across the
> application code and cluster configuration.
> It would be highly beneficial if such information would be part of the
> persisted metadata to not track these external pointers.
> It would also be great to persist the metadata information in a standardized
> format so that external projects don't need to use Flink's metadata
> serializers to access it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
