You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@flink.apache.org by al...@apache.org on 2020/06/10 10:37:05 UTC

[flink] 01/04: [FLINK-16213] Move stateful-stream-processing.md introduction to form "What is State" section

This is an automated email from the ASF dual-hosted git repository.

aljoscha pushed a commit to branch release-1.11
in repository https://gitbox.apache.org/repos/asf/flink.git

commit 3cc3310ae683be0b829fb67ba84d89398cdb9cf1
Author: Aljoscha Krettek <al...@apache.org>
AuthorDate: Tue Jun 9 12:52:41 2020 +0200

    [FLINK-16213] Move stateful-stream-processing.md introduction to form "What is State" section
---
 docs/concepts/stateful-stream-processing.md | 12 +++++-------
 1 file changed, 5 insertions(+), 7 deletions(-)

diff --git a/docs/concepts/stateful-stream-processing.md b/docs/concepts/stateful-stream-processing.md
index b8cdd63..7648791 100644
--- a/docs/concepts/stateful-stream-processing.md
+++ b/docs/concepts/stateful-stream-processing.md
@@ -24,6 +24,11 @@ specific language governing permissions and limitations
 under the License.
 -->
 
+* This will be replaced by the TOC
+{:toc}
+
+## What is State?
+
 While many operations in a dataflow simply look at one individual *event at a
 time* (for example an event parser), some operations remember information
 across multiple events (for example window operators). These operations are
@@ -54,13 +59,6 @@ When working with state, it might also be useful to read about [Flink's state
 backends]({% link ops/state/state_backends.md %}). Flink
 provides different state backends that specify how and where state is stored.
 
-* This will be replaced by the TOC
-{:toc}
-
-## What is State?
-
-`TODO: expand this section`
-
 {% top %}
 
 ## State in Stream & Batch Processing