Github user fhueske commented on a diff in the pull request:
https://github.com/apache/flink/pull/3191#discussion_r98028663
--- Diff: docs/dev/windows.md ---
@@ -795,15 +821,17 @@ necessarily the ones that arrive first or last.
## Allowed Lateness
-When working with *event-time* windowing it can happen that elements
arrive late, *i.e.* the watermark that Flink uses to
+When working with *event-time* windowing, it can happen that elements
arrive late, *i.e.* the watermark that Flink uses to
keep track of the progress of event-time is already past the end timestamp
of a window to which an element belongs. See
[event time](./event_time.html) and especially [late
elements](./event_time.html#late-elements) for a more thorough
discussion of how Flink deals with event time.
-By default, late elements are dropped if their associated window was
already evaluated. However,
+By default, late elements are dropped when the watermark is past the end
of the window. However,
Flink allows to specify a maximum *allowed lateness* for window operators.
Allowed lateness
-specifies by how much time elements can be late before they are dropped.
Elements that arrive
-within the allowed lateness of a window are still added to the window and
trigger an immediate evaluation of the window which might emit elements.
+specifies by how much time elements can be late before they are dropped,
and its default value is 0.
+Elements that arrive after the watermark is past the end of the window but
before it passes the end of
--- End diff --
"after the watermark is past the end" -> "after the watermark passed the
end"
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
