This is an automated email from the ASF dual-hosted git repository.
aljoscha pushed a commit to branch release-1.12
in repository https://gitbox.apache.org/repos/asf/flink.git
The following commit(s) were added to refs/heads/release-1.12 by this push:
new bd99991 [hotfix] Fix WatermarkStrategy explanation in execution mode
docs
bd99991 is described below
commit bd99991fdf8db806ba9645080f56e2ffc950f981
Author: Aljoscha Krettek <[email protected]>
AuthorDate: Thu Dec 17 11:42:29 2020 +0100
[hotfix] Fix WatermarkStrategy explanation in execution mode docs
---
docs/dev/datastream_execution_mode.md | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/docs/dev/datastream_execution_mode.md
b/docs/dev/datastream_execution_mode.md
index e09c936..afc5b13 100644
--- a/docs/dev/datastream_execution_mode.md
+++ b/docs/dev/datastream_execution_mode.md
@@ -258,8 +258,9 @@ streaming, in `BATCH` we can assume “perfect watermarks”.
Given the above, in `BATCH` mode, we only need a `MAX_WATERMARK` at the end of
the input associated with each key, or at the end of input if the input stream
is not keyed. Based on this scheme, all registered timers will fire at the *end
-of time* and user-defined `WatermarkAssigners` or `WatermarkStrategies` are
-ignored.
+of time* and user-defined `WatermarkAssigners` or `WatermarkGenerators` are
+ignored. Specifying a `WatermarkStrategy` is still important, though, because
+its `TimestampAssigner` will still be used to assign timestamps to records.
### Processing Time
