You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Nicholas Jiang (Jira)" <ji...@apache.org> on 2023/02/23 07:05:00 UTC
[jira] [Updated] (FLINK-31194) Introduces savepoint mechanism of Table Store
[ https://issues.apache.org/jira/browse/FLINK-31194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nicholas Jiang updated FLINK-31194:
-----------------------------------
Summary: Introduces savepoint mechanism of Table Store (was: ntroduces savepoint mechanism of Table Store)
> Introduces savepoint mechanism of Table Store
> ---------------------------------------------
>
> Key: FLINK-31194
> URL: https://issues.apache.org/jira/browse/FLINK-31194
> Project: Flink
> Issue Type: New Feature
> Components: Table Store
> Affects Versions: table-store-0.4.0
> Reporter: Nicholas Jiang
> Priority: Major
> Fix For: table-store-0.4.0
>
>
> Disaster Recovery is very much mission critical for any software. Especially when it comes to data systems, the impact could be very serious leading to delay in business decisions or even wrong business decisions at times. Flink Table Store could introduce savepoint mechanism to assist users in recovering data from a previous state.
> As the name suggest, "savepoint" saves the table as of the snapshot, so that it lets you restore the table to this savepoint at a later point in snapshot if need be. Care is taken to ensure cleaner will not clean up any files that are savepointed. On similar lines, savepoint cannot be triggered on a snapshot that is already cleaned up. In simpler terms, this is synonymous to taking a backup, just that we don't make a new copy of the table, but just save the state of the table elegantly so that we can restore it later when in need.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)