flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Johannes Moser (Jira)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-22256) Persist checkpoint type information
Date Tue, 11 May 2021 09:06:00 GMT

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

Johannes Moser commented on FLINK-22256:

[~trohrmann] & [~fabian.paul], can you please provide further information on this ticket?

_When & how_ would you need _which information_ in order to do _what_?
 * Where would you access the API?
 * How would you imagine it?
 * Which information about checkpoints/savepoints would you need?
 * How is the information used?

> 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

View raw message