[GitHub] zentol closed pull request #7364: [hotfix][doc] Replace currentLowWatermark with currentInputWatermark

[GitBox <gi...@apache.org>]

zentol closed pull request #7364: [hotfix][doc] Replace currentLowWatermark with currentInputWatermark
URL: https://github.com/apache/flink/pull/7364
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git a/docs/monitoring/debugging_event_time.md b/docs/monitoring/debugging_event_time.md
index 10a3fb20fdb..8ac72ebe663 100644
--- a/docs/monitoring/debugging_event_time.md
+++ b/docs/monitoring/debugging_event_time.md
@@ -33,13 +33,13 @@ is tracked within the system.
 
 Low watermarks of each task can be accessed through Flink web interface or [metrics system]({{ site.baseurl }}/monitoring/metrics.html).
 
-Each Task in Flink exposes a metric called `currentLowWatermark` that represents the lowest watermark received
+Each Task in Flink exposes a metric called `currentInputWatermark` that represents the lowest watermark received
 by this task. This long value represents the "current event time".
 The value is calculated by taking the minimum of all watermarks received by upstream operators. This means that 
 the event time tracked with watermarks is always dominated by the furthest-behind source.
 
 The low watermark metric is accessible **using the web interface**, by choosing a task in the metric tab,
-and selecting the `<taskNr>.currentLowWatermark` metric. In the new box you'll now be able to see 
+and selecting the `<taskNr>.currentInputWatermark` metric. In the new box you'll now be able to see 
 the current low watermark of the task.
 
 Another way of getting the metric is using one of the **metric reporters**, as described in the documentation


 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services