[
https://issues.apache.org/jira/browse/FLINK-23441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-23441:
-----------------------------------
Labels: pull-request-available stale-assigned (was: pull-request-available)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issue is assigned but has not
received an update in 30 days, so it has been labeled "stale-assigned".
If you are still working on the issue, please remove the label and add a
comment updating the community on your progress. If this issue is waiting on
feedback, please consider this a reminder to the committer/reviewer. Flink is a
very active project, and so we appreciate your patience.
If you are no longer working on the issue, please unassign yourself so someone
else may work on it.
> Remove CheckpointOptions Argument away from Snapshotable#snapshot
> -----------------------------------------------------------------
>
> Key: FLINK-23441
> URL: https://issues.apache.org/jira/browse/FLINK-23441
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / State Backends
> Reporter: Yuan Mei
> Assignee: Yuan Mei
> Priority: Major
> Labels: pull-request-available, stale-assigned
>
> CheckpointOptions contain many fields that are not related to the backend
> snapshot (materialization in changelog):
> alignment type, alignedCheckpointTimeout, and even
> CheckpointStorageLocationReference
> (the location is provided by/included in the #StreamFactory# already, we do
> not use CheckpointStorageLocationReference in away place in snapshotting.
> =================================
> In the future, if we want to separate checkpointing away from materialization
> (conceptually, they are indeed two different pieces as well), we do not need
> to provide such CheckpointOptions for each snapshotting.
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
