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

Posted to issues@flink.apache.org by "Caizhi Weng (Jira)" <ji...@apache.org> on 2022/04/06 07:17:00 UTC

[jira] [Created] (FLINK-27085) Introduce snapshot.num-retained.min option

Caizhi Weng created FLINK-27085:
-----------------------------------

             Summary: Introduce snapshot.num-retained.min option
                 Key: FLINK-27085
                 URL: https://issues.apache.org/jira/browse/FLINK-27085
             Project: Flink
          Issue Type: Sub-task
          Components: Table Store
    Affects Versions: 0.1.0
            Reporter: Caizhi Weng
             Fix For: 0.1.0


Currently we retain at least 1 snapshot when expiring. However consider the following scenario:

A user writes a snapshot one day ago. Today he is reading this snapshot and meanwhile writing more records. If a new snapshot is created and the reading is not finished, the old snapshot created one day ago will be removed as it exceeds maximum retaining time. This will cause the reading to fail.

We should introduce {{snapshot.num-retained.min}} to at least retain a minimum number of snapshots to avoid this problem.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)