zentol closed pull request #7363: [hotfix][docs] fix typo in udf and exec_conf 
doc
URL: https://github.com/apache/flink/pull/7363
 
 
   

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/dev/execution_configuration.md 
b/docs/dev/execution_configuration.md
index f0103b0f39f..fc2364bdfa0 100644
--- a/docs/dev/execution_configuration.md
+++ b/docs/dev/execution_configuration.md
@@ -51,7 +51,7 @@ With the closure cleaner disabled, it might happen that an 
anonymous user functi
 
 - `getNumberOfExecutionRetries()` / `setNumberOfExecutionRetries(int 
numberOfExecutionRetries)` Sets the number of times that failed tasks are 
re-executed. A value of zero effectively disables fault tolerance. A value of 
`-1` indicates that the system default value (as defined in the configuration) 
should be used. This is deprecated, use [restart strategies]({{ site.baseurl 
}}/dev/restart_strategies.html) instead.
 
-- `getExecutionRetryDelay()` / `setExecutionRetryDelay(long 
executionRetryDelay)` Sets the delay in milliseconds that the system waits 
after a job has failed, before re-executing it. The delay starts after all 
tasks have been successfully been stopped on the TaskManagers, and once the 
delay is past, the tasks are re-started. This parameter is useful to delay 
re-execution in order to let certain time-out related failures surface fully 
(like broken connections that have not fully timed out), before attempting a 
re-execution and immediately failing again due to the same problem. This 
parameter only has an effect if the number of execution re-tries is one or 
more. This is deprecated, use [restart strategies]({{ site.baseurl 
}}/dev/restart_strategies.html) instead.
+- `getExecutionRetryDelay()` / `setExecutionRetryDelay(long 
executionRetryDelay)` Sets the delay in milliseconds that the system waits 
after a job has failed, before re-executing it. The delay starts after all 
tasks have been successfully stopped on the TaskManagers, and once the delay is 
past, the tasks are re-started. This parameter is useful to delay re-execution 
in order to let certain time-out related failures surface fully (like broken 
connections that have not fully timed out), before attempting a re-execution 
and immediately failing again due to the same problem. This parameter only has 
an effect if the number of execution re-tries is one or more. This is 
deprecated, use [restart strategies]({{ site.baseurl 
}}/dev/restart_strategies.html) instead.
 
 - `getExecutionMode()` / `setExecutionMode()`. The default execution mode is 
PIPELINED. Sets the execution mode to execute the program. The execution mode 
defines whether data exchanges are performed in a batch or on a pipelined 
manner.
 
diff --git a/docs/dev/table/udfs.md b/docs/dev/table/udfs.md
index f2f6b7bcedd..44b8d431c8d 100644
--- a/docs/dev/table/udfs.md
+++ b/docs/dev/table/udfs.md
@@ -466,7 +466,7 @@ abstract class AggregateFunction[T, ACC] extends 
UserDefinedFunction {
     */
   def getValue(accumulator: ACC): T // MANDATORY
 
-  h/**
+  /**
     * Resets the accumulator for this [[AggregateFunction]]. This function 
must be implemented for
     * dataset grouping aggregate.
     *


 

----------------------------------------------------------------
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:
[email protected]


With regards,
Apache Git Services

Reply via email to