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

["Jingsong Lee (Jira)" <ji...@apache.org>]

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

Jingsong Lee closed FLINK-27085.
--------------------------------
    Resolution: Fixed

master: b3efd4f70e59b9d8069fecf13f506e72ed9a3e8d

> 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: table-store-0.1.0
>            Reporter: Caizhi Weng
>            Assignee: Caizhi Weng
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: table-store-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)