This is an automated email from the ASF dual-hosted git repository. git-site-role pushed a commit to branch asf-site in repository https://gitbox.apache.org/repos/asf/beam.git
The following commit(s) were added to refs/heads/asf-site by this push: new 443d050 Publishing website 2019/01/23 21:58:46 at commit dbda6ca 443d050 is described below commit 443d050ec38b0747a2a72e85f595bf3513c4b29f Author: jenkins <bui...@apache.org> AuthorDate: Wed Jan 23 21:58:47 2019 +0000 Publishing website 2019/01/23 21:58:46 at commit dbda6ca --- website/generated-content/documentation/programming-guide/index.html | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/website/generated-content/documentation/programming-guide/index.html b/website/generated-content/documentation/programming-guide/index.html index 3f2b048..1927924 100644 --- a/website/generated-content/documentation/programming-guide/index.html +++ b/website/generated-content/documentation/programming-guide/index.html @@ -3025,8 +3025,9 @@ outside that range (data from 5:00 or later) belong to a different window.</p> <p>However, data isn’t always guaranteed to arrive in a pipeline in time order, or to always arrive at predictable intervals. Beam tracks a <em>watermark</em>, 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 <strong>late data</strong>.</p> +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 +<strong>late data</strong>.</p> <p>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