This is an automated email from the ASF dual-hosted git repository. sjwiesman pushed a commit to branch release-1.13 in repository https://gitbox.apache.org/repos/asf/flink.git
The following commit(s) were added to refs/heads/release-1.13 by this push: new e015753 [hotfix][docs] Update release notes for 1.13 with state backend migration details e015753 is described below commit e01575337bfe12e40644b0aeff9fa89e9e00ffd1 Author: Seth Wiesman <sjwies...@gmail.com> AuthorDate: Fri Jul 9 15:29:12 2021 -0500 [hotfix][docs] Update release notes for 1.13 with state backend migration details Co-authored-by: David Anderson <da...@alpinegizmo.com> --- docs/content.zh/release-notes/flink-1.13.md | 15 ++++++++++++++- docs/content/release-notes/flink-1.13.md | 17 ++++++++++++++++- 2 files changed, 30 insertions(+), 2 deletions(-) diff --git a/docs/content.zh/release-notes/flink-1.13.md b/docs/content.zh/release-notes/flink-1.13.md index 13def89..dceda51 100644 --- a/docs/content.zh/release-notes/flink-1.13.md +++ b/docs/content.zh/release-notes/flink-1.13.md @@ -38,6 +38,20 @@ by default before) and there is no option to configure a synchronous snapshot an The constructors of `FsStateBackend` and `MemoryStateBackend` that take a flag for sync/async snapshots are kept for API compatibility, but the flags are ignored now. +##### [FLINK-19463](https://issues.apache.org/jira/browse/FLINK-19463) + +Flink has always separated local state storage from fault tolerance. +Keyed state is maintained locally in state backends, either on the JVM heap or in embedded RocksDB instances. +Fault tolerance comes from checkpoints and savepoints - periodic snapshots of a job's internal state to some durable file system - such as Amazon S3 or HDFS. + +Historically, Flink's `StateBackend` interface intermixed these concepts in a way that confused many users. +In 1.13, checkpointing configurations have been extracted into their own interface, `CheckpointStorage`. + +This change does not affect the runtime behavior and simply provides a better mental model to users. +Pipelines can be updated to use the new the new abstractions without losing state, consistency, or change in semantics. + +Please follow the [migration guide](https://ci.apache.org/projects/flink/flink-docs-release-1.13/docs/ops/state/state_backends/#migrating-from-legacy-backends) or the JavaDoc on the deprecated state backend classes - `MemoryStateBackend`, `FsStateBackend` and `RocksDBStateBackend` for migration details. + #### Unify binary format for Keyed State savepoints ##### [FLINK-20976](https://issues.apache.org/jira/browse/FLINK-20976) @@ -299,4 +313,3 @@ recovered. The community decided to deprecate the Apache Mesos support for Apache Flink. It is subject to removal in the future. Users are encouraged to switch to a different resource manager. - diff --git a/docs/content/release-notes/flink-1.13.md b/docs/content/release-notes/flink-1.13.md index 13def89..1798564 100644 --- a/docs/content/release-notes/flink-1.13.md +++ b/docs/content/release-notes/flink-1.13.md @@ -38,6 +38,22 @@ by default before) and there is no option to configure a synchronous snapshot an The constructors of `FsStateBackend` and `MemoryStateBackend` that take a flag for sync/async snapshots are kept for API compatibility, but the flags are ignored now. +#### Disentangle StateBackends from Checkpointing + +##### [FLINK-19463](https://issues.apache.org/jira/browse/FLINK-19463) + +Flink has always separated local state storage from fault tolerance. +Keyed state is maintained locally in state backends, either on the JVM heap or in embedded RocksDB instances. +Fault tolerance comes from checkpoints and savepoints - periodic snapshots of a job's internal state to some durable file system - such as Amazon S3 or HDFS. + +Historically, Flink's `StateBackend` interface intermixed these concepts in a way that confused many users. +In 1.13, checkpointing configurations have been extracted into their own interface, `CheckpointStorage`. + +This change does not affect the runtime behavior and simply provides a better mental model to users. +Pipelines can be updated to use the new the new abstractions without losing state, consistency, or change in semantics. + +Please follow the [migration guide](https://ci.apache.org/projects/flink/flink-docs-release-1.13/docs/ops/state/state_backends/#migrating-from-legacy-backends) or the JavaDoc on the deprecated state backend classes - `MemoryStateBackend`, `FsStateBackend` and `RocksDBStateBackend` for migration details. + #### Unify binary format for Keyed State savepoints ##### [FLINK-20976](https://issues.apache.org/jira/browse/FLINK-20976) @@ -299,4 +315,3 @@ recovered. The community decided to deprecate the Apache Mesos support for Apache Flink. It is subject to removal in the future. Users are encouraged to switch to a different resource manager. -