From 994e20620d2232ddf29f18900571d669104ae855 Mon Sep 17 00:00:00 2001 From: Junrui Lee Date: Sat, 25 Jan 2025 12:31:20 +0800 Subject: [PATCH] Revert "A typo mistake on 'Configuring a State Backend' section has been fixed." This reverts commit e2bc7c9e5b9b0531ba0c215790579c8a4c801d94. --- docs/content/docs/ops/state/state_backends.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/docs/ops/state/state_backends.md b/docs/content/docs/ops/state/state_backends.md index 6594018422f02..b62ace457e8d3 100644 --- a/docs/content/docs/ops/state/state_backends.md +++ b/docs/content/docs/ops/state/state_backends.md @@ -110,7 +110,7 @@ take a savepoint with the new version, and only after that you can restore it wi ## Configuring a State Backend -The default state backend, if you specify nothing, is the `HashMapStateBackend`. If you wish to establish a different default for all jobs on your cluster, you can do so by defining a new default state backend in [**Flink configuration file**]({{< ref "docs/deployment/config#flink-configuration-file" >}}). The default state backend can be overridden on a per-job basis, as shown below. +The default state backend, if you specify nothing, is the jobmanager. If you wish to establish a different default for all jobs on your cluster, you can do so by defining a new default state backend in [**Flink configuration file**]({{< ref "docs/deployment/config#flink-configuration-file" >}}). The default state backend can be overridden on a per-job basis, as shown below. ### Setting the Per-job State Backend