[jira] [Updated] (FLINK-28732) Deprecate ambiguous StateTTLConfig#cleanFullSnapshot API

["lincoln lee (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-28732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

lincoln lee updated FLINK-28732:
--------------------------------
    Fix Version/s: 1.20.0

> 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.19.0, 1.20.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)