This is an automated email from the ASF dual-hosted git repository.
kenn pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/beam.git
The following commit(s) were added to refs/heads/master by this push:
new 58de816 Improve programming model documentation.
new dbda6ca Merge pull request #7556: Improve programming model
documentation.
58de816 is described below
commit 58de816455ce6fd658b4086ecd20a579b6480c2d
Author: amaliujia <amaliu...@users.noreply.github.com>
AuthorDate: Thu Jan 17 20:11:19 2019 -0800
Improve programming model documentation.
---
website/src/documentation/programming-guide.md | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/website/src/documentation/programming-guide.md
b/website/src/documentation/programming-guide.md
index b637b19..45fb6ee 100644
--- a/website/src/documentation/programming-guide.md
+++ b/website/src/documentation/programming-guide.md
@@ -2421,8 +2421,9 @@ outside that range (data from 5:00 or later) belong to a
different window.
However, data isn't always guaranteed to arrive in a pipeline in time order, or
to always arrive at predictable intervals. Beam tracks a _watermark_, which is
the system's notion of when all data in a certain window can be expected to
have
-arrived in the pipeline. Data that arrives with a timestamp after the watermark
-is considered **late data**.
+arrived in the pipeline. Once the watermark progresses past the end of a
window,
+any further element that arrives with a timestamp in that window is considered
+**late data**.
From our example, suppose we have a simple watermark that assumes approximately
30s of lag time between the data timestamps (the event time) and the time the
