aljoscha commented on a change in pull request #12253:
URL: https://github.com/apache/flink/pull/12253#discussion_r429213190
##########
File path: docs/dev/event_timestamp_extractors.md
##########
@@ -25,83 +25,80 @@ under the License.
* toc
{:toc}
-As described in [timestamps and watermark handling]({{ site.baseurl
}}/dev/event_timestamps_watermarks.html),
-Flink provides abstractions that allow the programmer to assign their own
timestamps and emit their own watermarks. More specifically,
-one can do so by implementing one of the `AssignerWithPeriodicWatermarks` and
`AssignerWithPunctuatedWatermarks` interfaces, depending
-on the use case. In a nutshell, the first will emit watermarks periodically,
while the second does so based on some property of
-the incoming records, e.g. whenever a special element is encountered in the
stream.
+As described in [Generating Watermarks]({{ site.baseurl
+}}/dev/event_timestamps_watermarks.html), Flink provides abstractions that
+allow the programmer to assign their own timestamps and emit their own
+watermarks. More specifically, one can do so by implementing the
+`WatermarkGenerator` interface.
-In order to further ease the programming effort for such tasks, Flink comes
with some pre-implemented timestamp assigners.
-This section provides a list of them. Apart from their out-of-the-box
functionality, their implementation can serve as an example
-for custom implementations.
+In order to further ease the programming effort for such tasks, Flink comes
+with some pre-implemented timestamp assigners. This section provides a list of
+them. Apart from their out-of-the-box functionality, their implementation can
+serve as an example for custom implementations.
-### **Assigners with ascending timestamps**
+## Monotonously Increasing Timestamps
-The simplest special case for *periodic* watermark generation is the case
where timestamps seen by a given source task
-occur in ascending order. In that case, the current timestamp can always act
as a watermark, because no earlier timestamps will
-arrive.
+The simplest special case for *periodic* watermark generation is the case where
Review comment:
In my defense: this is existing copy that I just reused... 😅
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]