This is an automated email from the ASF dual-hosted git repository. dwysakowicz pushed a commit to branch release-1.12 in repository https://gitbox.apache.org/repos/asf/flink.git
commit 8faec59047e78664dba58d8dfe5f378f5ddbfb02 Author: Dawid Wysakowicz <[email protected]> AuthorDate: Tue Dec 1 18:13:26 2020 +0100 [FLINK-20423] Fix remaining occurences of site.baseurl This closes #14235 --- docs/dev/execution_configuration.md | 4 ++-- docs/dev/execution_configuration.zh.md | 4 ++-- docs/dev/table/sql/queries.md | 8 ++++---- docs/dev/table/sql/queries.zh.md | 8 ++++---- docs/dev/table/sqlClient.md | 4 ++-- docs/dev/table/sqlClient.zh.md | 2 +- docs/dev/table/streaming/joins.md | 4 ++-- 7 files changed, 17 insertions(+), 17 deletions(-) diff --git a/docs/dev/execution_configuration.md b/docs/dev/execution_configuration.md index 1b1b52b..147b0f7 100644 --- a/docs/dev/execution_configuration.md +++ b/docs/dev/execution_configuration.md @@ -50,9 +50,9 @@ With the closure cleaner disabled, it might happen that an anonymous user functi - `getMaxParallelism()` / `setMaxParallelism(int parallelism)` Set the default maximum parallelism for the job. This setting determines the maximum degree of parallelism and specifies the upper limit for dynamic scaling. -- `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]({% link redirects/restart_strategies.md %}) instead. +- `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]({% link dev/task_failure_recovery.md %}#restart-strategies) 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), be [...] +- `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), be [...] - `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/execution_configuration.zh.md b/docs/dev/execution_configuration.zh.md index cd5aa3a..55341a4 100644 --- a/docs/dev/execution_configuration.zh.md +++ b/docs/dev/execution_configuration.zh.md @@ -50,9 +50,9 @@ With the closure cleaner disabled, it might happen that an anonymous user functi - `getMaxParallelism()` / `setMaxParallelism(int parallelism)` Set the default maximum parallelism for the job. This setting determines the maximum degree of parallelism and specifies the upper limit for dynamic scaling. -- `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]({% link redirects/restart_strategies.zh.md %}) instead. +- `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]({% link dev/task_failure_recovery.zh.md %}#restart-strategies) 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), be [...] +- `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), be [...] - `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/sql/queries.md b/docs/dev/table/sql/queries.md index 07ca765..76a6fa0 100644 --- a/docs/dev/table/sql/queries.md +++ b/docs/dev/table/sql/queries.md @@ -726,12 +726,12 @@ FROM Orders LEFT JOIN LATERAL TABLE(unnest_udtf(tags)) ON TRUE <span class="label label-primary">Batch</span> <span class="label label-primary">Streaming</span> </td> <td> - <p><a href="{{ site.baseurl }}/dev/table/streaming/temporal_tables.html">Temporal Tables</a> are tables that track changes over time. - A <a href="{{ site.baseurl }}/dev/table/streaming/temporal_tables.html#temporal-table">Temporal Table</a> provides access to the versions of a temporal table at a specific point in time.</p> + <p><a href="{% link dev/table/streaming/temporal_tables.md %}">Temporal Tables</a> are tables that track changes over time. + A <a href="{% link dev/table/streaming/temporal_tables.md %}#temporal-table">Temporal Table</a> provides access to the versions of a temporal table at a specific point in time.</p> <p>Processing-time temporal join and event-time temporal join are supported, inner join and left join are supported.</p> <p>The event-time temporal join is not suppored in <span class="label label-primary">Batch</span></p> - <p>The following example assumes that <strong>LatestRates</strong> is a <a href="{{ site.baseurl }}/dev/table/streaming/temporal_tables.html#temporal-table">Temporal Table</a> which is materialized with the latest rate.</p> + <p>The following example assumes that <strong>LatestRates</strong> is a <a href="{% link dev/table/streaming/temporal_tables.md %}#temporal-table">Temporal Table</a> which is materialized with the latest rate.</p> {% highlight sql %} SELECT o.amount, o.currency, r.rate, o.amount * r.rate @@ -741,7 +741,7 @@ FROM ON r.currency = o.currency {% endhighlight %} <p>The RHS table can be named with an alias using optional clause <code>[[<strong>AS</strong>] correlationName]</code>, note that the <code><strong>AS</strong></code> keyword is also optional.</p> - <p>For more information please check the more detailed <a href="{{ site.baseurl }}/dev/table/streaming/temporal_tables.html">Temporal Tables</a> concept description.</p> + <p>For more information please check the more detailed <a href="{% link dev/table/streaming/temporal_tables.md %}">Temporal Tables</a> concept description.</p> <p>Only supported in Blink planner.</p> </td> </tr> diff --git a/docs/dev/table/sql/queries.zh.md b/docs/dev/table/sql/queries.zh.md index 804086b..cb17869 100644 --- a/docs/dev/table/sql/queries.zh.md +++ b/docs/dev/table/sql/queries.zh.md @@ -725,12 +725,12 @@ FROM Orders LEFT JOIN LATERAL TABLE(unnest_udtf(tags)) AS t(tag) ON TRUE <span class="label label-primary">批处理</span> <span class="label label-primary">流处理</span> </td> <td> - <p><a href="{{ site.baseurl }}/zh/dev/table/streaming/temporal_tables.html">Temporal Tables</a> 是随时间变化而变化的表。 - <a href="{{ site.baseurl }}/zh/dev/table/streaming/temporal_tables.html#temporal-table">Temporal Table</a> 提供访问指定时间点的 temporal table 版本的功能。</p> + <p><a href="{% link dev/table/streaming/temporal_tables.zh.md %}">Temporal Tables</a> 是随时间变化而变化的表。 + <a href="{% link dev/table/streaming/temporal_tables.zh.md %}#temporal-table">Temporal Table</a> 提供访问指定时间点的 temporal table 版本的功能。</p> <p>支持基于处理时间 或 基于事件时间 的 temporal table join, 支持 inner 和 left join。 </p> <p>基于事件时间的 temporal table join 在 <span class="label label-primary">批处理</span> 中暂不支持。</p> - <p>下述示例中，假设 <strong>LatestRates</strong> 是一个根据最新的 rates 物化的 <a href="{{ site.baseurl }}/zh/dev/table/streaming/temporal_tables.html#temporal-table">Temporal Table</a> 。</p> + <p>下述示例中，假设 <strong>LatestRates</strong> 是一个根据最新的 rates 物化的 <a href="{% link dev/table/streaming/temporal_tables.zh.md %}#temporal-table">Temporal Table</a> 。</p> {% highlight sql %} SELECT o.amount, o.currency, r.rate, o.amount * r.rate @@ -740,7 +740,7 @@ FROM ON r.currency = o.currency {% endhighlight %} <p>Join 的右表可以使用可选表达式 <code>[[<strong>AS</strong>] correlationName]</code> 取别名，注意 <code><strong>AS</strong></code> 关键词也是可选的。</p> - <p>请阅读 <a href="{{ site.baseurl }}/zh/dev/table/streaming/temporal_tables.html">Temporal Tables</a> 概念描述以了解详细信息。</p> + <p>请阅读 <a href="{% link dev/table/streaming/temporal_tables.zh.md %}">Temporal Tables</a> 概念描述以了解详细信息。</p> <p>仅 Blink planner 支持。</p> </td> </tr> diff --git a/docs/dev/table/sqlClient.md b/docs/dev/table/sqlClient.md index 9c8f5e9..4179062 100644 --- a/docs/dev/table/sqlClient.md +++ b/docs/dev/table/sqlClient.md @@ -380,7 +380,7 @@ CLI commands > session environment file > defaults environment file #### Restart Strategies -Restart strategies control how Flink jobs are restarted in case of a failure. Similar to [global restart strategies]({% link redirects/restart_strategies.md %}) for a Flink cluster, a more fine-grained restart configuration can be declared in an environment file. +Restart strategies control how Flink jobs are restarted in case of a failure. Similar to [global restart strategies]({% link dev/task_failure_recovery.md %}#restart-strategies) for a Flink cluster, a more fine-grained restart configuration can be declared in an environment file. The following strategies are supported: @@ -633,7 +633,7 @@ Job ID: 6f922fe5cba87406ff23ae4a7bb79044 Web interface: http://localhost:8081 {% endhighlight %} -<span class="label label-danger">Attention</span> The SQL Client does not track the status of the running Flink job after submission. The CLI process can be shutdown after the submission without affecting the detached query. Flink's [restart strategy]({% link redirects/restart_strategies.md %}) takes care of the fault-tolerance. A query can be cancelled using Flink's web interface, command-line, or REST API. +<span class="label label-danger">Attention</span> The SQL Client does not track the status of the running Flink job after submission. The CLI process can be shutdown after the submission without affecting the detached query. Flink's [restart strategy]({% link dev/task_failure_recovery.md %}#restart-strategies) takes care of the fault-tolerance. A query can be cancelled using Flink's web interface, command-line, or REST API. {% top %} diff --git a/docs/dev/table/sqlClient.zh.md b/docs/dev/table/sqlClient.zh.md index 7ea4221..5b54283 100644 --- a/docs/dev/table/sqlClient.zh.md +++ b/docs/dev/table/sqlClient.zh.md @@ -381,7 +381,7 @@ CLI commands > session environment file > defaults environment file #### 重启策略（Restart Strategies） -重启策略控制 Flink 作业失败时的重启方式。与 Flink 集群的[全局重启策略]({% link dev/task_failure_recovery.zh.md %})相似，更细精度的重启配置可以在环境配置文件中声明。 +重启策略控制 Flink 作业失败时的重启方式。与 Flink 集群的[全局重启策略]({% link dev/task_failure_recovery.zh.md %}#restart-strategies)相似，更细精度的重启配置可以在环境配置文件中声明。 Flink 支持以下策略： diff --git a/docs/dev/table/streaming/joins.md b/docs/dev/table/streaming/joins.md index 7f92b9a..3406d71 100644 --- a/docs/dev/table/streaming/joins.md +++ b/docs/dev/table/streaming/joins.md @@ -68,7 +68,7 @@ Compared to a regular join operation, this kind of join only supports append-onl Temporal Joins -------------- <span class="label label-danger">Attention</span> This feature is only supported in Blink planner. -<span class="label label-danger">Attention</span> Temporal table has two ways to define in Flink, i.e. [temporal table function]({% link dev/table/streaming/temporal_tables.md %}#temporal-table-function) and [temporal table DDL](({% link dev/table/streaming/temporal_tables.md %}#temporal-table-ddl)). +<span class="label label-danger">Attention</span> Temporal table has two ways to define in Flink, i.e. [temporal table function]({% link dev/table/streaming/temporal_tables.md %}#temporal-table-function) and [temporal table DDL]({% link dev/table/streaming/temporal_tables.md %}#temporal-table-ddl)). Temporal join that using temporal table function is only supported in Table API, temporal join that using temporal table DDL is only supported in SQL, please see the page [temporal table]({% link dev/table/streaming/temporal_tables.md %}) for more information about the differences between temporal table function and temporal table DDL. Temporal join is an arbitrary table (left input/probe side) correlate with the versions of temporal table (right input/build side), The temporal table can be an external dimension table that changes over time @@ -98,7 +98,7 @@ is joined with the version of the build side table at time `12:30:00` according Thus, the incoming row is only joined with rows that have a timestamp lower or equal to `12:30:00` with applied updates according to the primary key until this point in time. -By definition of event time, [watermarks]({{ site.baseurl }}/dev/event_time.html) allow the join operation to move +By definition of event time, [watermarks]({% link dev/event_time.md %}) allow the join operation to move forward in time and discard versions of the build table that are no longer necessary because no incoming row with lower or equal timestamp is expected.
