[flink] branch release-1.11 updated: [minor] Propagate recent changes to chinese documentation

[al...@apache.org]

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


The following commit(s) were added to refs/heads/release-1.11 by this push:
     new 3165418  [minor] Propagate recent changes to chinese documentation
3165418 is described below

commit 3165418fb0ab2f7ffd17d380a7c462fb10001a58
Author: Aljoscha Krettek <al...@apache.org>
AuthorDate: Wed Jun 10 12:42:31 2020 +0200

    [minor] Propagate recent changes to chinese documentation
---
 docs/concepts/stateful-stream-processing.zh.md | 26 +++++---------------------
 docs/concepts/timely-stream-processing.zh.md   | 14 +++++++++-----
 2 files changed, 14 insertions(+), 26 deletions(-)

diff --git a/docs/concepts/stateful-stream-processing.zh.md b/docs/concepts/stateful-stream-processing.zh.md
index e7d19ad..d991e83 100644
--- a/docs/concepts/stateful-stream-processing.zh.md
+++ b/docs/concepts/stateful-stream-processing.zh.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,19 +59,6 @@ When working with state, it might also be useful to read about [Flink's state
 backends]({% link ops/state/state_backends.zh.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
-
-`TODO: What is this section about? Do we even need it?`
-
 {% top %}
 
 ## Keyed State
@@ -252,8 +244,6 @@ See [Restart Strategies]({% link dev/task_failure_recovery.zh.md
 
 ### State Backends
 
-`TODO: expand this section`
-
 The exact data structures in which the key/values indexes are stored depends on
 the chosen [state backend]({% link
 ops/state/state_backends.zh.md %}). One state backend stores data in an in-memory
@@ -270,8 +260,6 @@ logic.
 
 ### Savepoints
 
-`TODO: expand this section`
-
 All programs that use checkpointing can resume execution from a **savepoint**.
 Savepoints allow both updating your programs and your Flink cluster without
 losing any state.
@@ -312,10 +300,6 @@ give *exactly once* guarantees even in *at least once* mode.
 
 {% top %}
 
-## End-to-end Exactly-Once Programs
-
-`TODO: add`
-
 ## State and Fault Tolerance in Batch Programs
 
 Flink executes [batch programs](../dev/batch/index.html) as a special case of
diff --git a/docs/concepts/timely-stream-processing.zh.md b/docs/concepts/timely-stream-processing.zh.md
index 9f80f72..38bab79 100644
--- a/docs/concepts/timely-stream-processing.zh.md
+++ b/docs/concepts/timely-stream-processing.zh.md
@@ -24,16 +24,20 @@ specific language governing permissions and limitations
 under the License.
 -->
 
-`TODO: add introduction`
-
 * This will be replaced by the TOC
 {:toc}
 
-## Latency & Completeness
+## Introduction
 
-`TODO: add these two sections`
+Timely steam processing is an extension of [stateful stream processing]({% link
+concepts/stateful-stream-processing.zh.md %}) in which time plays some role in the
+computation. Among other things, this is the case when you do time series
+analysis, when doing aggregations based on certain time periods (typically
+called windows), or when you do event processing where the time when an event
+occured is important.
 
-### Latency vs. Completeness in Batch & Stream Processing
+In the following sections we will highlight some of the topics that you should
+consider when working with timely Flink Applications.
 
 {% top %}