[
https://issues.apache.org/jira/browse/FLINK-28732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-28732:
-----------------------------------
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.
> Deprecate ambiguous StateTTLConfig#cleanFullSnapshot API
> --------------------------------------------------------
>
> Key: FLINK-28732
> URL: https://issues.apache.org/jira/browse/FLINK-28732
> Project: Flink
> Issue Type: Improvement
> Affects Versions: 1.15.0, 1.15.1
> Reporter: Yun Tang
> Assignee: Yun Tang
> Priority: Major
> Labels: pull-request-available, stale-assigned
> Fix For: 1.18.0
>
>
> After we introduce the native savepoint in flink-1.15, the semantics of the
> full snapshot changed. "Full snapshot" mainly refers to the newly "Canonical
> Savepoint", and the previous API of
> {{StateTTLConfig.Builder#cleanupFullSnapshot}}
> ([https://nightlies.apache.org/flink/flink-docs-release-1.15/docs/dev/datastream/fault-tolerance/state/#cleanup-in-full-snapshot)]
> becomes ambiguous. Even we trigger a native savepoint, we cannot cleanup
> expired data in the generated snapshot.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
