You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@flink.apache.org by "Yun Tang (Jira)" <ji...@apache.org> on 2022/07/28 13:01:00 UTC

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

Yun Tang created FLINK-28732:
--------------------------------

             Summary: 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.1, 1.15.0
            Reporter: Yun Tang
            Assignee: Yun Tang
             Fix For: 1.16.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)