You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@flink.apache.org by ch...@apache.org on 2023/02/06 15:52:21 UTC
[flink-web] 01/02: ref -> relref
This is an automated email from the ASF dual-hosted git repository.
chesnay pushed a commit to branch asf-staging
in repository https://gitbox.apache.org/repos/asf/flink-web.git
commit 0fb7a1ac75ef6959b04fec8d45334c04e3c10ce7
Author: Chesnay Schepler <ch...@apache.org>
AuthorDate: Mon Feb 6 16:51:22 2023 +0100
ref -> relref
---
docs/content.zh/_index.md | 12 ++++++------
docs/content.zh/community.md | 4 ++--
docs/content.zh/getting-help.md | 4 ++--
.../how-to-contribute/code-style-and-quality-common.md | 16 ++++++++--------
.../code-style-and-quality-components.md | 14 +++++++-------
.../code-style-and-quality-formatting.md | 14 +++++++-------
.../how-to-contribute/code-style-and-quality-java.md | 14 +++++++-------
.../how-to-contribute/code-style-and-quality-preamble.md | 14 +++++++-------
.../code-style-and-quality-pull-requests.md | 14 +++++++-------
.../how-to-contribute/code-style-and-quality-scala.md | 14 +++++++-------
.../how-to-contribute/contribute-documentation.md | 2 +-
docs/content.zh/how-to-contribute/overview.md | 14 +++++++-------
docs/content.zh/how-to-contribute/reviewing-prs.md | 8 ++++----
docs/content.zh/powered-by.md | 2 +-
docs/content.zh/what-is-flink/flink-applications.md | 4 ++--
docs/content.zh/what-is-flink/flink-architecture.md | 4 ++--
docs/content/_index.md | 12 ++++++------
docs/content/community.md | 4 ++--
docs/content/getting-help.md | 4 ++--
.../how-to-contribute/code-style-and-quality-common.md | 16 ++++++++--------
.../code-style-and-quality-components.md | 14 +++++++-------
.../code-style-and-quality-formatting.md | 14 +++++++-------
.../how-to-contribute/code-style-and-quality-java.md | 14 +++++++-------
.../how-to-contribute/code-style-and-quality-preamble.md | 14 +++++++-------
.../code-style-and-quality-pull-requests.md | 14 +++++++-------
.../how-to-contribute/code-style-and-quality-scala.md | 14 +++++++-------
docs/content/how-to-contribute/contribute-code.md | 14 +++++++-------
.../how-to-contribute/contribute-documentation.md | 2 +-
docs/content/how-to-contribute/overview.md | 16 ++++++++--------
docs/content/how-to-contribute/reviewing-prs.md | 8 ++++----
docs/content/posts/2023-01-26-release-1.16.1.md | 2 +-
docs/content/powered-by.md | 2 +-
docs/content/what-is-flink/flink-applications.md | 4 ++--
docs/content/what-is-flink/flink-architecture.md | 4 ++--
34 files changed, 163 insertions(+), 163 deletions(-)
diff --git a/docs/content.zh/_index.md b/docs/content.zh/_index.md
index fae3a0460..7e8f5c306 100644
--- a/docs/content.zh/_index.md
+++ b/docs/content.zh/_index.md
@@ -37,7 +37,7 @@ under the License.
<li>流批分析</li>
<li>数据管道 & ETL</li>
</ul>
- <a href={{< ref "use-cases" >}}>了解更多</a>
+ <a href={{< relref "use-cases" >}}>了解更多</a>
</div>
</div>
@@ -52,7 +52,7 @@ under the License.
<li>事件时间处理</li>
<li>成熟的迟到数据处理</li>
</ul>
- <a href="{{< ref "what-is-flink/flink-applications" >}}#building-blocks-for-streaming-applications">了解更多</a>
+ <a href="{{< relref "what-is-flink/flink-applications" >}}#building-blocks-for-streaming-applications">了解更多</a>
</div>
</div>
@@ -67,7 +67,7 @@ under the License.
<li>DataStream API & DataSet API</li>
<li>ProcessFunction (Time & State)</li>
</ul>
- <a href="{{< ref "what-is-flink/flink-applications" >}}#layered-apis">了解更多</a>
+ <a href="{{< relref "what-is-flink/flink-applications" >}}#layered-apis">了解更多</a>
</div>
</div>
{{< /columns >}}
@@ -83,7 +83,7 @@ under the License.
<li>高可用</li>
<li>保存点</li>
</ul>
- <a href="{{< ref "what-is-flink/flink-operations" >}}">了解更多</a>
+ <a href="{{< relref "what-is-flink/flink-operations" >}}">了解更多</a>
</div>
</div>
@@ -98,7 +98,7 @@ under the License.
<li>支持超大状态</li>
<li>增量检查点机制</li>
</ul>
- <a href="{{< ref "what-is-flink/flink-architecture" >}}#run-applications-at-any-scale">了解更多</a>
+ <a href="{{< relref "what-is-flink/flink-architecture" >}}#run-applications-at-any-scale">了解更多</a>
</div>
</div>
@@ -113,7 +113,7 @@ under the License.
<li>高吞吐</li>
<li>内存计算</li>
</ul>
- <a href="{{< ref "what-is-flink/flink-architecture" >}}#leverage-in-memory-performance">了解更多</a>
+ <a href="{{< relref "what-is-flink/flink-architecture" >}}#leverage-in-memory-performance">了解更多</a>
</div>
</div>
{{< /columns >}}
diff --git a/docs/content.zh/community.md b/docs/content.zh/community.md
index 570bc79ca..d3d71656e 100644
--- a/docs/content.zh/community.md
+++ b/docs/content.zh/community.md
@@ -120,7 +120,7 @@ under the License.
## 如何从 Apache Flink 获得帮助？
-我们可以通过多种方式从 Apache Flink 社区获得帮助。Flink committer 主要活跃在 [邮件列表](#mailing-lists)。对于用户支持和问题咨询，则可以通过 用户邮件列表 获得帮助。你还可以加入社区专属的 [Slack](#slack)。有些 Committer 同时会关注 [Stack Overflow](#stack-overflow)。请在提问的时候记得添加 *[apache-flink](http://stackoverflow.com/questions/tagged/apache-flink)* 的标签。问题反馈以及新特性的讨论则可以在 开发邮件列表 或者 [Jira](https://issues.apache.org/jira/browse/FLINK) 上进行讨论。有兴趣对 Flink 进行贡献的人请查阅 [贡献指南]({{< ref "how-to-contribute" >}}).
+我们可以通过多种方式从 Apache Flink 社区获得帮助。Flink committer 主要活跃在 [邮件列表](#mailing-lists)。对于用户支持和问题咨询，则可以通过 用户邮件列表 获得帮助。你还可以加入社区专属的 [Slack](#slack)。有些 Committer 同时会关注 [Stack Overflow](#stack-overflow)。请在提问的时候记得添加 *[apache-flink](http://stackoverflow.com/questions/tagged/apache-flink)* 的标签。问题反馈以及新特性的讨论则可以在 开发邮件列表 或者 [Jira](https://issues.apache.org/jira/browse/FLINK) 上进行讨论。有兴趣对 Flink 进行贡献的人请查阅 [贡献指南]({{< relref "how-to-contribute" >}}).
## 邮件列表
@@ -276,4 +276,4 @@ Flink Forward 大会每年都会在世界的不同地方举办。关于大会最
## 素材以及 Apache Flink Logo
-[素材页面]({{< ref "material" >}}) 提供了不同尺寸以及不同颜色的 Apache Flink Logo。
+[素材页面]({{< relref "material" >}}) 提供了不同尺寸以及不同颜色的 Apache Flink Logo。
diff --git a/docs/content.zh/getting-help.md b/docs/content.zh/getting-help.md
index 0f63e28ee..6924c579f 100644
--- a/docs/content.zh/getting-help.md
+++ b/docs/content.zh/getting-help.md
@@ -49,7 +49,7 @@ Apache Flink 社区每天都会回答许多用户的问题。你可以从历史
你可以通过 [此链接](https://join.slack.com/t/apache-flink/shared_invite/zt-1llkzbgyt-K2nNGGg88rfsDGLkT09Qzg) 加入 Apache Flink 社区专属的 Slack 工作空间。
在成功加入后，不要忘记在 #introductions 频道介绍你自己。
-Slack 规定每个邀请链接最多可邀请 100 人，如果遇到上述链接失效的情况，请联系 [Dev 邮件列表]({{< ref "community" >}}#mailing-lists)。
+Slack 规定每个邀请链接最多可邀请 100 人，如果遇到上述链接失效的情况，请联系 [Dev 邮件列表]({{< relref "community" >}}#mailing-lists)。
所有已经加入社区 Slack 空间的成员同样可以邀请新成员加入。
### Stack Overflow
@@ -60,7 +60,7 @@ Flink 社区的许多成员都活跃在 [Stack Overflow](https://stackoverflow.c
如果你发现一个意外行为可能是由 Bug 导致的，你可以在 [Flink's JIRA](https://issues.apache.org/jira/browse/FLINK) 中搜索已经上报的 Bug 或者发布该 Bug。
-如果你不确定意外行为的发生是否由 Bug 引起的，请发送问题到 [用户邮件列表]({{< ref "community" >}}#user-mailing-list)。
+如果你不确定意外行为的发生是否由 Bug 引起的，请发送问题到 [用户邮件列表]({{< relref "community" >}}#user-mailing-list)。
## 收到错误信息?
diff --git a/docs/content.zh/how-to-contribute/code-style-and-quality-common.md b/docs/content.zh/how-to-contribute/code-style-and-quality-common.md
index b5ebc1215..d90f229eb 100644
--- a/docs/content.zh/how-to-contribute/code-style-and-quality-common.md
+++ b/docs/content.zh/how-to-contribute/code-style-and-quality-common.md
@@ -6,13 +6,13 @@ bookHidden: true
# Code Style and Quality Guide — Common Rules
-#### [序言]({{< ref "how-to-contribute/code-style-and-quality-preamble" >}})
-#### [Pull Requests & Changes]({{< ref "how-to-contribute/code-style-and-quality-pull-requests" >}})
-#### [常用编码指南]({{< ref "how-to-contribute/code-style-and-quality-common" >}})
-#### [Java 语言指南]({{< ref "how-to-contribute/code-style-and-quality-java" >}})
-#### [Scala 语言指南]({{< ref "how-to-contribute/code-style-and-quality-scala" >}})
-#### [组件指南]({{< ref "how-to-contribute/code-style-and-quality-components" >}})
-#### [格式指南]({{< ref "how-to-contribute/code-style-and-quality-formatting" >}})
+#### [序言]({{< relref "how-to-contribute/code-style-and-quality-preamble" >}})
+#### [Pull Requests & Changes]({{< relref "how-to-contribute/code-style-and-quality-pull-requests" >}})
+#### [常用编码指南]({{< relref "how-to-contribute/code-style-and-quality-common" >}})
+#### [Java 语言指南]({{< relref "how-to-contribute/code-style-and-quality-java" >}})
+#### [Scala 语言指南]({{< relref "how-to-contribute/code-style-and-quality-scala" >}})
+#### [组件指南]({{< relref "how-to-contribute/code-style-and-quality-components" >}})
+#### [格式指南]({{< relref "how-to-contribute/code-style-and-quality-formatting" >}})
<hr>
@@ -173,7 +173,7 @@ For nullability, the Flink codebase aims to follow these conventions:
_Note: This means that `@Nonnull` annotations are usually not necessary, but can be used in certain cases to override a previous annotation, or to point non-nullability out in a context where one would expect a nullable value._
`Optional` is a good solution as a return type for method that may or may not have a result, so nullable return types are good candidates to be replaced with `Optional`.
-See also [usage of Java Optional]({{< ref "how-to-contribute/code-style-and-quality-java" >}}#java-optional).
+See also [usage of Java Optional]({{< relref "how-to-contribute/code-style-and-quality-java" >}}#java-optional).
### Avoid Code Duplication
diff --git a/docs/content.zh/how-to-contribute/code-style-and-quality-components.md b/docs/content.zh/how-to-contribute/code-style-and-quality-components.md
index 212e9ec76..7e94499c7 100644
--- a/docs/content.zh/how-to-contribute/code-style-and-quality-components.md
+++ b/docs/content.zh/how-to-contribute/code-style-and-quality-components.md
@@ -6,13 +6,13 @@ bookHidden: true
# Apache Flink 代码样式和质量指南 — 组件
-#### [序言]({{< ref "how-to-contribute/code-style-and-quality-preamble" >}})
-#### [Pull Requests & Changes]({{< ref "how-to-contribute/code-style-and-quality-pull-requests" >}})
-#### [常用编码指南]({{< ref "how-to-contribute/code-style-and-quality-common" >}})
-#### [Java 语言指南]({{< ref "how-to-contribute/code-style-and-quality-java" >}})
-#### [Scala 语言指南]({{< ref "how-to-contribute/code-style-and-quality-scala" >}})
-#### [组件指南]({{< ref "how-to-contribute/code-style-and-quality-components" >}})
-#### [格式指南]({{< ref "how-to-contribute/code-style-and-quality-formatting" >}})
+#### [序言]({{< relref "how-to-contribute/code-style-and-quality-preamble" >}})
+#### [Pull Requests & Changes]({{< relref "how-to-contribute/code-style-and-quality-pull-requests" >}})
+#### [常用编码指南]({{< relref "how-to-contribute/code-style-and-quality-common" >}})
+#### [Java 语言指南]({{< relref "how-to-contribute/code-style-and-quality-java" >}})
+#### [Scala 语言指南]({{< relref "how-to-contribute/code-style-and-quality-scala" >}})
+#### [组件指南]({{< relref "how-to-contribute/code-style-and-quality-components" >}})
+#### [格式指南]({{< relref "how-to-contribute/code-style-and-quality-formatting" >}})
## 组件特定指南
diff --git a/docs/content.zh/how-to-contribute/code-style-and-quality-formatting.md b/docs/content.zh/how-to-contribute/code-style-and-quality-formatting.md
index 50801058f..9efa1c05f 100644
--- a/docs/content.zh/how-to-contribute/code-style-and-quality-formatting.md
+++ b/docs/content.zh/how-to-contribute/code-style-and-quality-formatting.md
@@ -6,13 +6,13 @@ bookHidden: true
# Code Style and Quality Guide — Formatting Guide
-#### [序言]({{< ref "how-to-contribute/code-style-and-quality-preamble" >}})
-#### [Pull Requests & Changes]({{< ref "how-to-contribute/code-style-and-quality-pull-requests" >}})
-#### [常用编码指南]({{< ref "how-to-contribute/code-style-and-quality-common" >}})
-#### [Java 语言指南]({{< ref "how-to-contribute/code-style-and-quality-java" >}})
-#### [Scala 语言指南]({{< ref "how-to-contribute/code-style-and-quality-scala" >}})
-#### [组件指南]({{< ref "how-to-contribute/code-style-and-quality-components" >}})
-#### [格式指南]({{< ref "how-to-contribute/code-style-and-quality-formatting" >}})
+#### [序言]({{< relref "how-to-contribute/code-style-and-quality-preamble" >}})
+#### [Pull Requests & Changes]({{< relref "how-to-contribute/code-style-and-quality-pull-requests" >}})
+#### [常用编码指南]({{< relref "how-to-contribute/code-style-and-quality-common" >}})
+#### [Java 语言指南]({{< relref "how-to-contribute/code-style-and-quality-java" >}})
+#### [Scala 语言指南]({{< relref "how-to-contribute/code-style-and-quality-scala" >}})
+#### [组件指南]({{< relref "how-to-contribute/code-style-and-quality-components" >}})
+#### [格式指南]({{< relref "how-to-contribute/code-style-and-quality-formatting" >}})
## Java Code Formatting Style
diff --git a/docs/content.zh/how-to-contribute/code-style-and-quality-java.md b/docs/content.zh/how-to-contribute/code-style-and-quality-java.md
index 0efa8d292..55dfd6ff6 100644
--- a/docs/content.zh/how-to-contribute/code-style-and-quality-java.md
+++ b/docs/content.zh/how-to-contribute/code-style-and-quality-java.md
@@ -6,13 +6,13 @@ bookHidden: true
# Code Style and Quality Guide — Java
-#### [序言]({{< ref "how-to-contribute/code-style-and-quality-preamble" >}})
-#### [Pull Requests & Changes]({{< ref "how-to-contribute/code-style-and-quality-pull-requests" >}})
-#### [常用编码指南]({{< ref "how-to-contribute/code-style-and-quality-common" >}})
-#### [Java 语言指南]({{< ref "how-to-contribute/code-style-and-quality-java" >}})
-#### [Scala 语言指南]({{< ref "how-to-contribute/code-style-and-quality-scala" >}})
-#### [组件指南]({{< ref "how-to-contribute/code-style-and-quality-components" >}})
-#### [格式指南]({{< ref "how-to-contribute/code-style-and-quality-formatting" >}})
+#### [序言]({{< relref "how-to-contribute/code-style-and-quality-preamble" >}})
+#### [Pull Requests & Changes]({{< relref "how-to-contribute/code-style-and-quality-pull-requests" >}})
+#### [常用编码指南]({{< relref "how-to-contribute/code-style-and-quality-common" >}})
+#### [Java 语言指南]({{< relref "how-to-contribute/code-style-and-quality-java" >}})
+#### [Scala 语言指南]({{< relref "how-to-contribute/code-style-and-quality-scala" >}})
+#### [组件指南]({{< relref "how-to-contribute/code-style-and-quality-components" >}})
+#### [格式指南]({{< relref "how-to-contribute/code-style-and-quality-formatting" >}})
## Java Language Features and Libraries
diff --git a/docs/content.zh/how-to-contribute/code-style-and-quality-preamble.md b/docs/content.zh/how-to-contribute/code-style-and-quality-preamble.md
index f73581627..b98003f8b 100644
--- a/docs/content.zh/how-to-contribute/code-style-and-quality-preamble.md
+++ b/docs/content.zh/how-to-contribute/code-style-and-quality-preamble.md
@@ -6,13 +6,13 @@ weight: 19
# Apache Flink Code Style and Quality Guide
-#### [序言]({{< ref "how-to-contribute/code-style-and-quality-preamble" >}})
-#### [Pull Requests & Changes]({{< ref "how-to-contribute/code-style-and-quality-pull-requests" >}})
-#### [常用编码指南]({{< ref "how-to-contribute/code-style-and-quality-common" >}})
-#### [Java 语言指南]({{< ref "how-to-contribute/code-style-and-quality-java" >}})
-#### [Scala 语言指南]({{< ref "how-to-contribute/code-style-and-quality-scala" >}})
-#### [组件指南]({{< ref "how-to-contribute/code-style-and-quality-components" >}})
-#### [格式指南]({{< ref "how-to-contribute/code-style-and-quality-formatting" >}})
+#### [序言]({{< relref "how-to-contribute/code-style-and-quality-preamble" >}})
+#### [Pull Requests & Changes]({{< relref "how-to-contribute/code-style-and-quality-pull-requests" >}})
+#### [常用编码指南]({{< relref "how-to-contribute/code-style-and-quality-common" >}})
+#### [Java 语言指南]({{< relref "how-to-contribute/code-style-and-quality-java" >}})
+#### [Scala 语言指南]({{< relref "how-to-contribute/code-style-and-quality-scala" >}})
+#### [组件指南]({{< relref "how-to-contribute/code-style-and-quality-components" >}})
+#### [格式指南]({{< relref "how-to-contribute/code-style-and-quality-formatting" >}})
<hr>
diff --git a/docs/content.zh/how-to-contribute/code-style-and-quality-pull-requests.md b/docs/content.zh/how-to-contribute/code-style-and-quality-pull-requests.md
index a09b8bf22..97396305a 100644
--- a/docs/content.zh/how-to-contribute/code-style-and-quality-pull-requests.md
+++ b/docs/content.zh/how-to-contribute/code-style-and-quality-pull-requests.md
@@ -6,13 +6,13 @@ bookHidden: true
# Code Style and Quality Guide — Pull Requests & Changes
-#### [序言]({{< ref "how-to-contribute/code-style-and-quality-preamble" >}})
-#### [Pull Requests & Changes]({{< ref "how-to-contribute/code-style-and-quality-pull-requests" >}})
-#### [常用编码指南]({{< ref "how-to-contribute/code-style-and-quality-common" >}})
-#### [Java 语言指南]({{< ref "how-to-contribute/code-style-and-quality-java" >}})
-#### [Scala 语言指南]({{< ref "how-to-contribute/code-style-and-quality-scala" >}})
-#### [组件指南]({{< ref "how-to-contribute/code-style-and-quality-components" >}})
-#### [格式指南]({{< ref "how-to-contribute/code-style-and-quality-formatting" >}})
+#### [序言]({{< relref "how-to-contribute/code-style-and-quality-preamble" >}})
+#### [Pull Requests & Changes]({{< relref "how-to-contribute/code-style-and-quality-pull-requests" >}})
+#### [常用编码指南]({{< relref "how-to-contribute/code-style-and-quality-common" >}})
+#### [Java 语言指南]({{< relref "how-to-contribute/code-style-and-quality-java" >}})
+#### [Scala 语言指南]({{< relref "how-to-contribute/code-style-and-quality-scala" >}})
+#### [组件指南]({{< relref "how-to-contribute/code-style-and-quality-components" >}})
+#### [格式指南]({{< relref "how-to-contribute/code-style-and-quality-formatting" >}})
<hr>
diff --git a/docs/content.zh/how-to-contribute/code-style-and-quality-scala.md b/docs/content.zh/how-to-contribute/code-style-and-quality-scala.md
index d7f177ef4..ab6f79371 100644
--- a/docs/content.zh/how-to-contribute/code-style-and-quality-scala.md
+++ b/docs/content.zh/how-to-contribute/code-style-and-quality-scala.md
@@ -6,13 +6,13 @@ bookHidden: true
# Code Style and Quality Guide — Scala
-#### [序言]({{< ref "how-to-contribute/code-style-and-quality-preamble" >}})
-#### [Pull Requests & Changes]({{< ref "how-to-contribute/code-style-and-quality-pull-requests" >}})
-#### [常用编码指南]({{< ref "how-to-contribute/code-style-and-quality-common" >}})
-#### [Java 语言指南]({{< ref "how-to-contribute/code-style-and-quality-java" >}})
-#### [Scala 语言指南]({{< ref "how-to-contribute/code-style-and-quality-scala" >}})
-#### [组件指南]({{< ref "how-to-contribute/code-style-and-quality-components" >}})
-#### [格式指南]({{< ref "how-to-contribute/code-style-and-quality-formatting" >}})
+#### [序言]({{< relref "how-to-contribute/code-style-and-quality-preamble" >}})
+#### [Pull Requests & Changes]({{< relref "how-to-contribute/code-style-and-quality-pull-requests" >}})
+#### [常用编码指南]({{< relref "how-to-contribute/code-style-and-quality-common" >}})
+#### [Java 语言指南]({{< relref "how-to-contribute/code-style-and-quality-java" >}})
+#### [Scala 语言指南]({{< relref "how-to-contribute/code-style-and-quality-scala" >}})
+#### [组件指南]({{< relref "how-to-contribute/code-style-and-quality-components" >}})
+#### [格式指南]({{< relref "how-to-contribute/code-style-and-quality-formatting" >}})
## Scala 语言特性
diff --git a/docs/content.zh/how-to-contribute/contribute-documentation.md b/docs/content.zh/how-to-contribute/contribute-documentation.md
index 98d63171a..0f64e24cd 100644
--- a/docs/content.zh/how-to-contribute/contribute-documentation.md
+++ b/docs/content.zh/how-to-contribute/contribute-documentation.md
@@ -26,7 +26,7 @@ git clone https://github.com/<your-user-name>/flink.git
…请确保已经有一个相对应的 [Jira](https://issues.apache.org/jira/browse/FLINK) issue 存在了。我们要求所有文档更改都需要关联一个 Jira issue，除了一些微不足道的修复，如拼写错误。
-同时，先阅读一下 [文档样式指南]({{< ref "how-to-contribute/documentation-style-guide" >}}) 能够很好的帮助你写出易懂、连贯和全面的文档。
+同时，先阅读一下 [文档样式指南]({{< relref "how-to-contribute/documentation-style-guide" >}}) 能够很好的帮助你写出易懂、连贯和全面的文档。
## 更新或扩展文档
diff --git a/docs/content.zh/how-to-contribute/overview.md b/docs/content.zh/how-to-contribute/overview.md
index 0aa416e0b..bf150f2f1 100644
--- a/docs/content.zh/how-to-contribute/overview.md
+++ b/docs/content.zh/how-to-contribute/overview.md
@@ -28,11 +28,11 @@ Apache Flink 是由一个开放友好的社区开发的。我们诚挚地欢迎
</tr>
<tr>
<td><span class="glyphicon glyphicon-console" aria-hidden="true"></span> 贡献代码</td>
- <td>请阅读 <a href=""{{< ref "how-to-contribute/contribute-code" >}}">代码贡献指南</a></td>
+ <td>请阅读 <a href=""{{< relref "how-to-contribute/contribute-code" >}}">代码贡献指南</a></td>
</tr>
<tr>
<td><span class="glyphicon glyphicon-ok" aria-hidden="true"></span> 帮助做代码审核</td>
- <td>请阅读 <a href="{{< ref "how-to-contribute/reviewing-prs" >}}">代码审核指南</a></td>
+ <td>请阅读 <a href="{{< relref "how-to-contribute/reviewing-prs" >}}">代码审核指南</a></td>
</tr>
<tr>
<td><span class="glyphicon glyphicon-thumbs-up" aria-hidden="true"></span> 帮助准备版本发布</td>
@@ -48,13 +48,13 @@ Apache Flink 是由一个开放友好的社区开发的。我们诚挚地欢迎
</tr>
<tr>
<td><span class="glyphicon glyphicon-list-alt" aria-hidden="true"></span> 贡献文档</td>
- <td>请阅读 <a href="{{< ref "how-to-contribute/contribute-documentation" >}}">文档贡献指南</a></td>
+ <td>请阅读 <a href="{{< relref "how-to-contribute/contribute-documentation" >}}">文档贡献指南</a></td>
</tr>
<tr>
<td><span class="glyphicon glyphicon-user" aria-hidden="true"></span> 支持 Flink 用户</td>
<td>
<ul class="contribute-card-list">
- <li>回答 <a href="{{< ref "community" >}}#mailing-lists">用户邮件列表</a> 中的问题</li>
+ <li>回答 <a href="{{< relref "community" >}}#mailing-lists">用户邮件列表</a> 中的问题</li>
<li>回答 <a href="https://stackoverflow.com/questions/tagged/apache-flink">Stack Overflow</a> 上带有 <a href="https://stackoverflow.com/questions/tagged/apache-flink"><code style="background-color: #cee0ed; border-color: #cee0ed;">apache-flink</code></a>、 <a href="https://stackoverflow.com/questions/tagged/flink-streaming"><code style="background-color: #cee0ed; border-color: #cee0ed;">flink-streaming</code></a> 或 <a href="https://stackoverflow.com/questions/tagged/flink-sql"><code [...]
<li>检查 <a href="http://issues.apache.org/jira/browse/FLINK">Jira</a> 上近期发布的 issue 中用户提出的问题</li>
</ul>
@@ -62,7 +62,7 @@ Apache Flink 是由一个开放友好的社区开发的。我们诚挚地欢迎
</tr>
<tr>
<td><span class="glyphicon glyphicon-blackboard" aria-hidden="true"></span> 改进网站</td>
- <td>请阅读 <a href="{{< ref "how-to-contribute/improve-website" >}}">网站贡献指南</a></td>
+ <td>请阅读 <a href="{{< relref "how-to-contribute/improve-website" >}}">网站贡献指南</a></td>
</tr>
<tr>
<td><span class="glyphicon glyphicon-volume-up" aria-hidden="true"></span> 推广 Flink</td>
@@ -70,13 +70,13 @@ Apache Flink 是由一个开放友好的社区开发的。我们诚挚地欢迎
<ul class="contribute-card-list">
<li>组织或出席 <a href="https://www.meetup.com/topics/apache-flink/">Flink Meetup</a></li>
<li>贡献 <a href="https://flink.apache.org/blog/">Flink blog</a></li>
- <li>在 <a href="{{< ref "community" >}}#mailing-lists">community@flink.apache.org 邮件列表</a>分享你的会议、聚会或博客文章，或发 tweet 并 <a href="https://twitter.com/ApacheFlink">@ApacheFlink</a>。</li>
+ <li>在 <a href="{{< relref "community" >}}#mailing-lists">community@flink.apache.org 邮件列表</a>分享你的会议、聚会或博客文章，或发 tweet 并 <a href="https://twitter.com/ApacheFlink">@ApacheFlink</a>。</li>
</ul>
</td>
</tr>
<tr>
<td colspan="2">
- <span class="glyphicon glyphicon-question-sign" aria-hidden="true"></span> 如有其他问题请到 <a href="{{< ref "community" >}}#mailing-lists">dev@flink.apache.org 邮件列表</a> 寻求帮助！
+ <span class="glyphicon glyphicon-question-sign" aria-hidden="true"></span> 如有其他问题请到 <a href="{{< relref "community" >}}#mailing-lists">dev@flink.apache.org 邮件列表</a> 寻求帮助！
</td>
</tr>
</tbody>
diff --git a/docs/content.zh/how-to-contribute/reviewing-prs.md b/docs/content.zh/how-to-contribute/reviewing-prs.md
index 0d23b5cb2..c3e0ecbea 100644
--- a/docs/content.zh/how-to-contribute/reviewing-prs.md
+++ b/docs/content.zh/how-to-contribute/reviewing-prs.md
@@ -19,7 +19,7 @@ weight: 18
### 1. 贡献的描述是否清晰？
-检查贡献是否有充分的描述以方便审核，不重要的更改和修复不需要很长的描述。如果实现方案完全是[按照之前在 Jira 或 dev 邮件列表上讨论结论]({{< ref "how-to-contribute/contribute-code" >}}#consensus)进行的话，只需要一个对讨论的简短的引用即可。 如果实现方案与之前达成一致的方案不同的话，关于实现的详细描述是需要的，以便 review 贡献时更深入地讨论。
+检查贡献是否有充分的描述以方便审核，不重要的更改和修复不需要很长的描述。如果实现方案完全是[按照之前在 Jira 或 dev 邮件列表上讨论结论]({{< relref "how-to-contribute/contribute-code" >}}#consensus)进行的话，只需要一个对讨论的简短的引用即可。 如果实现方案与之前达成一致的方案不同的话，关于实现的详细描述是需要的，以便 review 贡献时更深入地讨论。
任何改变功能或行为的 pull request 都需要描述这些改变的重点, 以便知道审核什么内容(并且不必钻研代码来了解更改的作用)。
@@ -29,7 +29,7 @@ weight: 18
### 2. 是否一致认为这一变更或者功能应该进入 Flink？
-这个问题要直接在关联的 Jira issue 中回答。对于在达成一致前创建的 pull request 来说，需要[先在 Jira 中寻求一致的意见]({{< ref "how-to-contribute/contribute-code" >}})。
+这个问题要直接在关联的 Jira issue 中回答。对于在达成一致前创建的 pull request 来说，需要[先在 Jira 中寻求一致的意见]({{< relref "how-to-contribute/contribute-code" >}})。
对于 `[hotfix]` 类型的的 pull request，可以在 pull request 中寻求意见一致。
@@ -72,7 +72,7 @@ weight: 18
* 代码是否避免引入额外的编译器警告？
* 如果依赖更新了，NOTICE 文件是否也更新了？
-可以在 [Flink代码样式和质量指南]({{< ref "how-to-contribute/code-style-and-quality-preamble" >}}) 中找到编码的规范和指南。
+可以在 [Flink代码样式和质量指南]({{< relref "how-to-contribute/code-style-and-quality-preamble" >}}) 中找到编码的规范和指南。
----
@@ -80,4 +80,4 @@ weight: 18
如果这个 pull request 引入了一个新功能，该功能应该被文档化。Flink 社区正在同时维护英文和中文文档。所以如果你想要更新或扩展文档，英文和中文文档都需要更新。如果你不熟悉中文，请创建一个用于中文文档翻译的 JIRA 并附上 `chinese-translation` 的组件名，并与当前 JIRA 关联起来。如果你熟悉中文，我们鼓励在一个 pull request 中同时更新两边的文档。
-阅读[如何贡献文档]({{< ref "how-to-contribute/contribute-documentation" >}})了解更多。
\ No newline at end of file
+阅读[如何贡献文档]({{< relref "how-to-contribute/contribute-documentation" >}})了解更多。
\ No newline at end of file
diff --git a/docs/content.zh/powered-by.md b/docs/content.zh/powered-by.md
index 67ab721bc..904b00c06 100644
--- a/docs/content.zh/powered-by.md
+++ b/docs/content.zh/powered-by.md
@@ -271,6 +271,6 @@ Apache Flink 为全球许多公司和企业的关键业务提供支持。在这
在项目的 wiki 页面中有一个 <a href="https://cwiki.apache.org/confluence/display/FLINK/Powered+by+Flink" target='_blank'><small><span class="glyphicon glyphicon-new-window"></span></small> 谁在使用 Flink</a> 的页面，展示了更多的 Flink 用户。请注意，该列表并不全面。我们只添加明确要求列出的用户。
-如果你希望加入此页面，请通过 [Flink 用户邮件列表]({{< ref "community" >}}) 告诉我们。
+如果你希望加入此页面，请通过 [Flink 用户邮件列表]({{< relref "community" >}}) 告诉我们。
{{< table_noheader "powered-by" >}}
diff --git a/docs/content.zh/what-is-flink/flink-applications.md b/docs/content.zh/what-is-flink/flink-applications.md
index 4116e2cc1..7dc02fad0 100644
--- a/docs/content.zh/what-is-flink/flink-applications.md
+++ b/docs/content.zh/what-is-flink/flink-applications.md
@@ -60,7 +60,7 @@ Flink 根据抽象程度分层，提供了三种不同的 API。每一种 API
### ProcessFunction
-{{< docs_link file="flink-docs-stable/dev/stream/operators/process_function.html" name="ProcessFunction">}} 是 Flink 所提供的最具表达力的接口。ProcessFunction 可以处理一或两条输入数据流中的单个事件或者归入一个特定窗口内的多个事件。它提供了对于时间和状态的细粒度控制。开发者可以在其中任意地修改状态，也能够注册定时器用以在未来的某一时刻触发回调函数。因此，你可以利用 ProcessFunction 实现许多[有状态的事件驱动应用]({{< ref "use-cases#eventDrivenApps" >}})所需要的基于单个事件的复杂业务逻辑。
+{{< docs_link file="flink-docs-stable/dev/stream/operators/process_function.html" name="ProcessFunction">}} 是 Flink 所提供的最具表达力的接口。ProcessFunction 可以处理一或两条输入数据流中的单个事件或者归入一个特定窗口内的多个事件。它提供了对于时间和状态的细粒度控制。开发者可以在其中任意地修改状态，也能够注册定时器用以在未来的某一时刻触发回调函数。因此，你可以利用 ProcessFunction 实现许多[有状态的事件驱动应用]({{< relref "use-cases#eventDrivenApps" >}})所需要的基于单个事件的复杂业务逻辑。
下面的代码示例展示了如何在 `KeyedStream` 上利用 `KeyedProcessFunction` 对标记为 `START` 和 `END` 的事件进行处理。当收到 `START` 事件时，处理函数会记录其时间戳，并且注册一个时长4小时的计时器。如果在计时器结束之前收到 `END` 事件，处理函数会计算其与上一个 `START` 事件的时间间隔，清空状态并将计算结果返回。否则，计时器结束，并清空状态。
@@ -157,7 +157,7 @@ DataStream<Tuple2<String, Long>> result = clicks
Flink 支持两种关系型的 API，{{< docs_link file="flink-docs-stable/dev/table/index.html" name="Table API 和 SQL">}}。这两个 API 都是批处理和流处理统一的 API，这意味着在无边界的实时数据流和有边界的历史记录数据流上，关系型 API 会以相同的语义执行查询，并产生相同的结果。Table API 和 SQL 借助了 [Apache Calcite](https://calcite.apache.org) 来进行查询的解析，校验以及优化。它们可以与 DataStream 和 DataSet API 无缝集成，并支持用户自定义的标量函数，聚合函数以及表值函数。
-Flink 的关系型 API 旨在简化[数据分析]({{< ref "use-cases#analytics" >}})、[数据流水线和 ETL 应用]({{< ref "use-cases#pipelines" >}})的定义。
+Flink 的关系型 API 旨在简化[数据分析]({{< relref "use-cases#analytics" >}})、[数据流水线和 ETL 应用]({{< relref "use-cases#pipelines" >}})的定义。
下面的代码示例展示了如何使用 SQL 语句查询捕获会话时间范围内所有的点击流事件，并对每一次会话的点击量进行计数。此示例与上述 DataStream API 中的示例有着相同的逻辑。
diff --git a/docs/content.zh/what-is-flink/flink-architecture.md b/docs/content.zh/what-is-flink/flink-architecture.md
index c59e9a2cc..43abc3f77 100644
--- a/docs/content.zh/what-is-flink/flink-architecture.md
+++ b/docs/content.zh/what-is-flink/flink-architecture.md
@@ -32,7 +32,7 @@ Apache Flink 是一个框架和分布式处理引擎，用于在*无边界和有
**Apache Flink 擅长处理无界和有界数据集** 精确的时间控制和状态化使得 Flink 的运行时(runtime)能够运行任何处理无界流的应用。有界流则由一些专为固定大小数据集特殊设计的算法和数据结构进行内部处理，产生了出色的性能。
-通过探索 Flink 之上构建的 [用例]({{< ref "use-cases" >}}) 来加深理解。
+通过探索 Flink 之上构建的 [用例]({{< relref "use-cases" >}}) 来加深理解。
## 部署应用到任意地方
@@ -61,7 +61,7 @@ Flink 提供了两种应用程序部署模式，即 *框架模式* 和 *库模
Flink 旨在任意规模上运行有状态流式应用。因此，应用程序被并行化为可能数千个任务，这些任务分布在集群中并发执行。所以应用程序能够充分利用无尽的 CPU、内存、磁盘和网络 IO。而且 Flink 很容易维护非常大的应用程序状态。其异步和增量的检查点算法对处理延迟产生最小的影响，同时保证精确一次状态的一致性。
-[Flink 用户报告了其生产环境中一些令人印象深刻的扩展性数字]({{< ref "powered-by" >}})
+[Flink 用户报告了其生产环境中一些令人印象深刻的扩展性数字]({{< relref "powered-by" >}})
* 处理**每天处理数万亿的事件**,
* 应用维护**几TB大小的状态**, 和
diff --git a/docs/content/_index.md b/docs/content/_index.md
index ca0c30788..85c8605dd 100644
--- a/docs/content/_index.md
+++ b/docs/content/_index.md
@@ -37,7 +37,7 @@ under the License.
<li>Stream & Batch Analytics</li>
<li>Data Pipelines & ETL</li>
</ul>
- <a href={{< ref "use-cases" >}}>Learn more</a>
+ <a href={{< relref "use-cases" >}}>Learn more</a>
</div>
</div>
@@ -52,7 +52,7 @@ under the License.
<li>Event-time processing</li>
<li>Sophisticated late data handling</li>
</ul>
- <a href="{{< ref "what-is-flink/flink-applications" >}}#building-blocks-for-streaming-applications">Learn more</a>
+ <a href="{{< relref "what-is-flink/flink-applications" >}}#building-blocks-for-streaming-applications">Learn more</a>
</div>
</div>
@@ -67,7 +67,7 @@ under the License.
<li>DataStream API & DataSet API</li>
<li>ProcessFunction (Time & State)</li>
</ul>
- <a href="{{< ref "what-is-flink/flink-applications" >}}#layered-apis">Learn more</a>
+ <a href="{{< relref "what-is-flink/flink-applications" >}}#layered-apis">Learn more</a>
</div>
</div>
{{< /columns >}}
@@ -83,7 +83,7 @@ under the License.
<li>High-availability setup</li>
<li>Savepoints</li>
</ul>
- <a href="{{< ref "what-is-flink/flink-operations" >}}">Learn more</a>
+ <a href="{{< relref "what-is-flink/flink-operations" >}}">Learn more</a>
</div>
</div>
@@ -98,7 +98,7 @@ under the License.
<li>Support for very large state</li>
<li>Incremental checkpointing</li>
</ul>
- <a href="{{< ref "what-is-flink/flink-architecture" >}}#run-applications-at-any-scale">Learn more</a>
+ <a href="{{< relref "what-is-flink/flink-architecture" >}}#run-applications-at-any-scale">Learn more</a>
</div>
</div>
@@ -113,7 +113,7 @@ under the License.
<li>High throughput</li>
<li>In-Memory computing</li>
</ul>
- <a href="{{< ref "what-is-flink/flink-architecture" >}}#leverage-in-memory-performance">Learn more</a>
+ <a href="{{< relref "what-is-flink/flink-architecture" >}}#leverage-in-memory-performance">Learn more</a>
</div>
</div>
{{< /columns >}}
diff --git a/docs/content/community.md b/docs/content/community.md
index a91a52d6c..b70581fcc 100644
--- a/docs/content/community.md
+++ b/docs/content/community.md
@@ -120,7 +120,7 @@ under the License.
## How do I get help from Apache Flink?
-There are many ways to get help from the Apache Flink community. The [mailing lists](#mailing-lists) are the primary place where all Flink committers are present. For user support and questions use the *user mailing list*. You can also join the community on [Slack](#slack). Some committers are also monitoring [Stack Overflow](#stack-overflow). Please remember to tag your questions with the *[apache-flink](http://stackoverflow.com/questions/tagged/apache-flink)* tag. Bugs and feature requ [...]
+There are many ways to get help from the Apache Flink community. The [mailing lists](#mailing-lists) are the primary place where all Flink committers are present. For user support and questions use the *user mailing list*. You can also join the community on [Slack](#slack). Some committers are also monitoring [Stack Overflow](#stack-overflow). Please remember to tag your questions with the *[apache-flink](http://stackoverflow.com/questions/tagged/apache-flink)* tag. Bugs and feature requ [...]
## Mailing Lists
@@ -280,4 +280,4 @@ Please find the most up-to-date list <a href="https://projects.apache.org/commit
## Materials / Apache Flink Logos
-The [materials page]({{< ref "material" >}}) offers assets such as the Apache Flink logo in different image formats, or the Flink color scheme.
+The [materials page]({{< relref "material" >}}) offers assets such as the Apache Flink logo in different image formats, or the Flink color scheme.
diff --git a/docs/content/getting-help.md b/docs/content/getting-help.md
index 3dbc2f522..e66b31148 100644
--- a/docs/content/getting-help.md
+++ b/docs/content/getting-help.md
@@ -49,7 +49,7 @@ Please note that you won't receive a respose to your mail if you are not subscri
You can join the [Apache Flink community on Slack.](https://join.slack.com/t/apache-flink/shared_invite/zt-1llkzbgyt-K2nNGGg88rfsDGLkT09Qzg)
After creating an account in Slack, don't forget to introduce yourself in #introductions.
-Due to Slack limitations the invite link expires after 100 invites. If it is expired, please reach out to the [Dev mailing list]({{< ref "community" >}}#mailing-lists).
+Due to Slack limitations the invite link expires after 100 invites. If it is expired, please reach out to the [Dev mailing list]({{< relref "community" >}}#mailing-lists).
Any existing Slack member can also invite anyone else to join.
### Stack Overflow
@@ -60,7 +60,7 @@ Many members of the Flink community are active on [Stack Overflow](https://stack
If you observe an unexpected behavior that might be caused by a bug, you can search for reported bugs or file a bug report in [Flink's JIRA](https://issues.apache.org/jira/browse/FLINK).
-If you are unsure whether the unexpected behavior happend due to a bug or not, please post a question to the [user mailing list]({{< ref "community" >}}#user-mailing-list).
+If you are unsure whether the unexpected behavior happend due to a bug or not, please post a question to the [user mailing list]({{< relref "community" >}}#user-mailing-list).
## Got an Error Message?
diff --git a/docs/content/how-to-contribute/code-style-and-quality-common.md b/docs/content/how-to-contribute/code-style-and-quality-common.md
index e11b28074..1ee1d376d 100644
--- a/docs/content/how-to-contribute/code-style-and-quality-common.md
+++ b/docs/content/how-to-contribute/code-style-and-quality-common.md
@@ -6,13 +6,13 @@ bookHidden: true
# Code Style and Quality Guide — Common Rules
-#### [Preamble]({{< ref "how-to-contribute/code-style-and-quality-preamble" >}})
-#### [Pull Requests & Changes]({{< ref "how-to-contribute/code-style-and-quality-pull-requests" >}})
-#### [Common Coding Guide]({{< ref "how-to-contribute/code-style-and-quality-common" >}})
-#### [Java Language Guide]({{< ref "how-to-contribute/code-style-and-quality-java" >}})
-#### [Scala Language Guide]({{< ref "how-to-contribute/code-style-and-quality-scala" >}})
-#### [Components Guide]({{< ref "how-to-contribute/code-style-and-quality-components" >}})
-#### [Formatting Guide]({{< ref "how-to-contribute/code-style-and-quality-formatting" >}})
+#### [Preamble]({{< relref "how-to-contribute/code-style-and-quality-preamble" >}})
+#### [Pull Requests & Changes]({{< relref "how-to-contribute/code-style-and-quality-pull-requests" >}})
+#### [Common Coding Guide]({{< relref "how-to-contribute/code-style-and-quality-common" >}})
+#### [Java Language Guide]({{< relref "how-to-contribute/code-style-and-quality-java" >}})
+#### [Scala Language Guide]({{< relref "how-to-contribute/code-style-and-quality-scala" >}})
+#### [Components Guide]({{< relref "how-to-contribute/code-style-and-quality-components" >}})
+#### [Formatting Guide]({{< relref "how-to-contribute/code-style-and-quality-formatting" >}})
<hr>
@@ -173,7 +173,7 @@ For nullability, the Flink codebase aims to follow these conventions:
_Note: This means that `@Nonnull` annotations are usually not necessary, but can be used in certain cases to override a previous annotation, or to point non-nullability out in a context where one would expect a nullable value._
`Optional` is a good solution as a return type for method that may or may not have a result, so nullable return types are good candidates to be replaced with `Optional`.
-See also [usage of Java Optional]({{< ref "how-to-contribute/code-style-and-quality-java" >}}#java-optional).
+See also [usage of Java Optional]({{< relref "how-to-contribute/code-style-and-quality-java" >}}#java-optional).
### Avoid Code Duplication
diff --git a/docs/content/how-to-contribute/code-style-and-quality-components.md b/docs/content/how-to-contribute/code-style-and-quality-components.md
index 02f0b7d9b..22e14ec49 100644
--- a/docs/content/how-to-contribute/code-style-and-quality-components.md
+++ b/docs/content/how-to-contribute/code-style-and-quality-components.md
@@ -6,13 +6,13 @@ bookHidden: true
# Code Style and Quality Guide — Components Guide
-#### [Preamble]({{< ref "how-to-contribute/code-style-and-quality-preamble" >}})
-#### [Pull Requests & Changes]({{< ref "how-to-contribute/code-style-and-quality-pull-requests" >}})
-#### [Common Coding Guide]({{< ref "how-to-contribute/code-style-and-quality-common" >}})
-#### [Java Language Guide]({{< ref "how-to-contribute/code-style-and-quality-java" >}})
-#### [Scala Language Guide]({{< ref "how-to-contribute/code-style-and-quality-scala" >}})
-#### [Components Guide]({{< ref "how-to-contribute/code-style-and-quality-components" >}})
-#### [Formatting Guide]({{< ref "how-to-contribute/code-style-and-quality-formatting" >}})
+#### [Preamble]({{< relref "how-to-contribute/code-style-and-quality-preamble" >}})
+#### [Pull Requests & Changes]({{< relref "how-to-contribute/code-style-and-quality-pull-requests" >}})
+#### [Common Coding Guide]({{< relref "how-to-contribute/code-style-and-quality-common" >}})
+#### [Java Language Guide]({{< relref "how-to-contribute/code-style-and-quality-java" >}})
+#### [Scala Language Guide]({{< relref "how-to-contribute/code-style-and-quality-scala" >}})
+#### [Components Guide]({{< relref "how-to-contribute/code-style-and-quality-components" >}})
+#### [Formatting Guide]({{< relref "how-to-contribute/code-style-and-quality-formatting" >}})
## Component Specific Guidelines
diff --git a/docs/content/how-to-contribute/code-style-and-quality-formatting.md b/docs/content/how-to-contribute/code-style-and-quality-formatting.md
index b2c30d849..d336c955d 100644
--- a/docs/content/how-to-contribute/code-style-and-quality-formatting.md
+++ b/docs/content/how-to-contribute/code-style-and-quality-formatting.md
@@ -6,13 +6,13 @@ bookHidden: true
# Code Style and Quality Guide — Formatting Guide
-#### [Preamble]({{< ref "how-to-contribute/code-style-and-quality-preamble" >}})
-#### [Pull Requests & Changes]({{< ref "how-to-contribute/code-style-and-quality-pull-requests" >}})
-#### [Common Coding Guide]({{< ref "how-to-contribute/code-style-and-quality-common" >}})
-#### [Java Language Guide]({{< ref "how-to-contribute/code-style-and-quality-java" >}})
-#### [Scala Language Guide]({{< ref "how-to-contribute/code-style-and-quality-scala" >}})
-#### [Components Guide]({{< ref "how-to-contribute/code-style-and-quality-components" >}})
-#### [Formatting Guide]({{< ref "how-to-contribute/code-style-and-quality-formatting" >}})
+#### [Preamble]({{< relref "how-to-contribute/code-style-and-quality-preamble" >}})
+#### [Pull Requests & Changes]({{< relref "how-to-contribute/code-style-and-quality-pull-requests" >}})
+#### [Common Coding Guide]({{< relref "how-to-contribute/code-style-and-quality-common" >}})
+#### [Java Language Guide]({{< relref "how-to-contribute/code-style-and-quality-java" >}})
+#### [Scala Language Guide]({{< relref "how-to-contribute/code-style-and-quality-scala" >}})
+#### [Components Guide]({{< relref "how-to-contribute/code-style-and-quality-components" >}})
+#### [Formatting Guide]({{< relref "how-to-contribute/code-style-and-quality-formatting" >}})
## Java Code Formatting Style
diff --git a/docs/content/how-to-contribute/code-style-and-quality-java.md b/docs/content/how-to-contribute/code-style-and-quality-java.md
index 16daf8cd5..a1cdb10ba 100644
--- a/docs/content/how-to-contribute/code-style-and-quality-java.md
+++ b/docs/content/how-to-contribute/code-style-and-quality-java.md
@@ -6,13 +6,13 @@ bookHidden: true
# Code Style and Quality Guide — Java
-#### [Preamble]({{< ref "how-to-contribute/code-style-and-quality-preamble" >}})
-#### [Pull Requests & Changes]({{< ref "how-to-contribute/code-style-and-quality-pull-requests" >}})
-#### [Common Coding Guide]({{< ref "how-to-contribute/code-style-and-quality-common" >}})
-#### [Java Language Guide]({{< ref "how-to-contribute/code-style-and-quality-java" >}})
-#### [Scala Language Guide]({{< ref "how-to-contribute/code-style-and-quality-scala" >}})
-#### [Components Guide]({{< ref "how-to-contribute/code-style-and-quality-components" >}})
-#### [Formatting Guide]({{< ref "how-to-contribute/code-style-and-quality-formatting" >}})
+#### [Preamble]({{< relref "how-to-contribute/code-style-and-quality-preamble" >}})
+#### [Pull Requests & Changes]({{< relref "how-to-contribute/code-style-and-quality-pull-requests" >}})
+#### [Common Coding Guide]({{< relref "how-to-contribute/code-style-and-quality-common" >}})
+#### [Java Language Guide]({{< relref "how-to-contribute/code-style-and-quality-java" >}})
+#### [Scala Language Guide]({{< relref "how-to-contribute/code-style-and-quality-scala" >}})
+#### [Components Guide]({{< relref "how-to-contribute/code-style-and-quality-components" >}})
+#### [Formatting Guide]({{< relref "how-to-contribute/code-style-and-quality-formatting" >}})
## Java Language Features and Libraries
diff --git a/docs/content/how-to-contribute/code-style-and-quality-preamble.md b/docs/content/how-to-contribute/code-style-and-quality-preamble.md
index 82e14230b..23eee1175 100644
--- a/docs/content/how-to-contribute/code-style-and-quality-preamble.md
+++ b/docs/content/how-to-contribute/code-style-and-quality-preamble.md
@@ -6,13 +6,13 @@ weight: 19
# Apache Flink Code Style and Quality Guide
-#### [Preamble]({{< ref "how-to-contribute/code-style-and-quality-preamble" >}})
-#### [Pull Requests & Changes]({{< ref "how-to-contribute/code-style-and-quality-pull-requests" >}})
-#### [Common Coding Guide]({{< ref "how-to-contribute/code-style-and-quality-common" >}})
-#### [Java Language Guide]({{< ref "how-to-contribute/code-style-and-quality-java" >}})
-#### [Scala Language Guide]({{< ref "how-to-contribute/code-style-and-quality-scala" >}})
-#### [Components Guide]({{< ref "how-to-contribute/code-style-and-quality-components" >}})
-#### [Formatting Guide]({{< ref "how-to-contribute/code-style-and-quality-formatting" >}})
+#### [Preamble]({{< relref "how-to-contribute/code-style-and-quality-preamble" >}})
+#### [Pull Requests & Changes]({{< relref "how-to-contribute/code-style-and-quality-pull-requests" >}})
+#### [Common Coding Guide]({{< relref "how-to-contribute/code-style-and-quality-common" >}})
+#### [Java Language Guide]({{< relref "how-to-contribute/code-style-and-quality-java" >}})
+#### [Scala Language Guide]({{< relref "how-to-contribute/code-style-and-quality-scala" >}})
+#### [Components Guide]({{< relref "how-to-contribute/code-style-and-quality-components" >}})
+#### [Formatting Guide]({{< relref "how-to-contribute/code-style-and-quality-formatting" >}})
<hr>
diff --git a/docs/content/how-to-contribute/code-style-and-quality-pull-requests.md b/docs/content/how-to-contribute/code-style-and-quality-pull-requests.md
index 5ef03f66b..194876d8e 100644
--- a/docs/content/how-to-contribute/code-style-and-quality-pull-requests.md
+++ b/docs/content/how-to-contribute/code-style-and-quality-pull-requests.md
@@ -6,13 +6,13 @@ bookHidden: true
# Code Style and Quality Guide — Pull Requests & Changes
-#### [Preamble]({{< ref "how-to-contribute/code-style-and-quality-preamble" >}})
-#### [Pull Requests & Changes]({{< ref "how-to-contribute/code-style-and-quality-pull-requests" >}})
-#### [Common Coding Guide]({{< ref "how-to-contribute/code-style-and-quality-common" >}})
-#### [Java Language Guide]({{< ref "how-to-contribute/code-style-and-quality-java" >}})
-#### [Scala Language Guide]({{< ref "how-to-contribute/code-style-and-quality-scala" >}})
-#### [Components Guide]({{< ref "how-to-contribute/code-style-and-quality-components" >}})
-#### [Formatting Guide]({{< ref "how-to-contribute/code-style-and-quality-formatting" >}})
+#### [Preamble]({{< relref "how-to-contribute/code-style-and-quality-preamble" >}})
+#### [Pull Requests & Changes]({{< relref "how-to-contribute/code-style-and-quality-pull-requests" >}})
+#### [Common Coding Guide]({{< relref "how-to-contribute/code-style-and-quality-common" >}})
+#### [Java Language Guide]({{< relref "how-to-contribute/code-style-and-quality-java" >}})
+#### [Scala Language Guide]({{< relref "how-to-contribute/code-style-and-quality-scala" >}})
+#### [Components Guide]({{< relref "how-to-contribute/code-style-and-quality-components" >}})
+#### [Formatting Guide]({{< relref "how-to-contribute/code-style-and-quality-formatting" >}})
<hr>
diff --git a/docs/content/how-to-contribute/code-style-and-quality-scala.md b/docs/content/how-to-contribute/code-style-and-quality-scala.md
index 81a1e8282..0390d5f7c 100644
--- a/docs/content/how-to-contribute/code-style-and-quality-scala.md
+++ b/docs/content/how-to-contribute/code-style-and-quality-scala.md
@@ -6,13 +6,13 @@ bookHidden: true
# Code Style and Quality Guide — Scala
-#### [Preamble]({{< ref "how-to-contribute/code-style-and-quality-preamble" >}})
-#### [Pull Requests & Changes]({{< ref "how-to-contribute/code-style-and-quality-pull-requests" >}})
-#### [Common Coding Guide]({{< ref "how-to-contribute/code-style-and-quality-common" >}})
-#### [Java Language Guide]({{< ref "how-to-contribute/code-style-and-quality-java" >}})
-#### [Scala Language Guide]({{< ref "how-to-contribute/code-style-and-quality-scala" >}})
-#### [Components Guide]({{< ref "how-to-contribute/code-style-and-quality-components" >}})
-#### [Formatting Guide]({{< ref "how-to-contribute/code-style-and-quality-formatting" >}})
+#### [Preamble]({{< relref "how-to-contribute/code-style-and-quality-preamble" >}})
+#### [Pull Requests & Changes]({{< relref "how-to-contribute/code-style-and-quality-pull-requests" >}})
+#### [Common Coding Guide]({{< relref "how-to-contribute/code-style-and-quality-common" >}})
+#### [Java Language Guide]({{< relref "how-to-contribute/code-style-and-quality-java" >}})
+#### [Scala Language Guide]({{< relref "how-to-contribute/code-style-and-quality-scala" >}})
+#### [Components Guide]({{< relref "how-to-contribute/code-style-and-quality-components" >}})
+#### [Formatting Guide]({{< relref "how-to-contribute/code-style-and-quality-formatting" >}})
## Scala Language Features
diff --git a/docs/content/how-to-contribute/contribute-code.md b/docs/content/how-to-contribute/contribute-code.md
index d35323e5b..038ff72b5 100644
--- a/docs/content/how-to-contribute/contribute-code.md
+++ b/docs/content/how-to-contribute/contribute-code.md
@@ -8,7 +8,7 @@ weight: 17
Apache Flink is maintained, improved, and extended by code contributions of volunteers. We welcome contributions to Flink, but due to the size of the project and to preserve the high quality of the code base, we follow a contribution process that is explained in this document.
-**Please feel free to ask questions at any time.** Either send a mail to the [Dev mailing list]({{< ref "community" >}}#mailing-lists) or comment on the Jira issue you are working on.
+**Please feel free to ask questions at any time.** Either send a mail to the [Dev mailing list]({{< relref "community" >}}#mailing-lists) or comment on the Jira issue you are working on.
**IMPORTANT**: Please read this document carefully before starting to work on a code contribution. Follow the process and guidelines explained below. Contributing to Apache Flink does not start with opening a pull request. We expect contributors to reach out to us first to discuss the overall approach together. Without consensus with the Flink committers, contributions might require substantial rework or will not be reviewed.
@@ -106,7 +106,7 @@ to the Flink project and want to learn about it and its contribution process, yo
<div class="panel panel-default">
<div class="panel-body">
<h2><span class="number">2</span><a href="#implement">Implement</a></h2>
- <p>Implement the change according to the <a href="{{< ref "how-to-contribute/contribute-code" >}}">Code Style and Quality Guide</a> and the approach agreed upon in the Jira ticket.</p> <br />
+ <p>Implement the change according to the <a href="{{< relref "how-to-contribute/contribute-code" >}}">Code Style and Quality Guide</a> and the approach agreed upon in the Jira ticket.</p> <br />
<p><b>Only start working on the implementation if there is consensus on the approach (e.g. you are assigned to the ticket)</b></p>
</div>
</div>
@@ -151,7 +151,7 @@ The first step for making a contribution to Apache Flink is to reach consensus w
In most cases, the discussion should happen in [Flink's bug tracker: Jira](https://issues.apache.org/jira/projects/FLINK/issues).
-The following types of changes require a `[DISCUSS]` thread on the [Flink Dev mailing list]({{< ref "community" >}}#mailing-lists):
+The following types of changes require a `[DISCUSS]` thread on the [Flink Dev mailing list]({{< relref "community" >}}#mailing-lists):
- big changes (major new feature; big refactorings, involving multiple components)
- potentially controversial changes or issues
@@ -184,9 +184,9 @@ Jira tickets based on a dev@ discussion need to link to that discussion and shou
- Impact on Flink's build time
- Dependencies and their licenses
-If a change is identified as a large or controversial change in the discussion on Jira, it might require a [Flink Improvement Proposal (FLIP)](https://cwiki.apache.org/confluence/display/FLINK/Flink+Improvement+Proposals) or a discussion on the [Dev mailing list]({{< ref "community" >}}#mailing-lists) to reach agreement and consensus.
+If a change is identified as a large or controversial change in the discussion on Jira, it might require a [Flink Improvement Proposal (FLIP)](https://cwiki.apache.org/confluence/display/FLINK/Flink+Improvement+Proposals) or a discussion on the [Dev mailing list]({{< relref "community" >}}#mailing-lists) to reach agreement and consensus.
-Contributors can expect to get a first reaction from a committer within a few days after opening the ticket. If a ticket doesn't get any attention, we recommend reaching out to the [developer mailing list]({{< ref "community" >}}#mailing-lists). Note that the Flink community sometimes does not have the capacity to accept all incoming contributions.
+Contributors can expect to get a first reaction from a committer within a few days after opening the ticket. If a ticket doesn't get any attention, we recommend reaching out to the [developer mailing list]({{< relref "community" >}}#mailing-lists). Note that the Flink community sometimes does not have the capacity to accept all incoming contributions.
Once all requirements for the ticket are met, a committer will assign somebody to the *`Assignee`* field of the ticket to work on it.
@@ -204,7 +204,7 @@ Once you've been assigned to a Jira issue, you may start to implement the requir
Here are some further points to keep in mind while implementing:
- [Set up a Flink development environment](https://cwiki.apache.org/confluence/display/FLINK/Setting+up+a+Flink+development+environment)
-- Follow the [Code Style and Quality Guide]({{< ref "how-to-contribute/contribute-code" >}}) of Flink
+- Follow the [Code Style and Quality Guide]({{< relref "how-to-contribute/contribute-code" >}}) of Flink
- Take any discussions and requirements from the Jira issue or design document into account.
- Do not mix unrelated issues into one contribution.
@@ -228,7 +228,7 @@ Considerations before or right after opening a pull request:
Code changes in Flink are reviewed and accepted through [GitHub pull requests](https://help.github.com/en/articles/creating-a-pull-request).
-There is a separate guide on [how to review a pull request]({{< ref "how-to-contribute/reviewing-prs" >}}), including our pull request review process. As a code author, you should prepare your pull request to meet all requirements.
+There is a separate guide on [how to review a pull request]({{< relref "how-to-contribute/reviewing-prs" >}}), including our pull request review process. As a code author, you should prepare your pull request to meet all requirements.
<a name="merge"></a>
diff --git a/docs/content/how-to-contribute/contribute-documentation.md b/docs/content/how-to-contribute/contribute-documentation.md
index f599b4af5..b4410a5c0 100644
--- a/docs/content/how-to-contribute/contribute-documentation.md
+++ b/docs/content/how-to-contribute/contribute-documentation.md
@@ -26,7 +26,7 @@ The documentation is located in the `docs/` subdirectory of the Flink code base.
... please make sure there exists a [Jira](https://issues.apache.org/jira/browse/FLINK) issue that corresponds to your contribution. We require all documentation changes to refer to a Jira issue, except for trivial fixes such as typos.
-Also, have a look at the [Documentation Style Guide]({{< ref "how-to-contribute/documentation-style-guide" >}}) for some guidance on how to write accessible, consistent and inclusive documentation.
+Also, have a look at the [Documentation Style Guide]({{< relref "how-to-contribute/documentation-style-guide" >}}) for some guidance on how to write accessible, consistent and inclusive documentation.
## Update or extend the documentation
diff --git a/docs/content/how-to-contribute/overview.md b/docs/content/how-to-contribute/overview.md
index 8e0d33392..17e38a959 100644
--- a/docs/content/how-to-contribute/overview.md
+++ b/docs/content/how-to-contribute/overview.md
@@ -28,11 +28,11 @@ Apache Flink is developed by an open and friendly community. Everybody is cordia
</tr>
<tr>
<td><span class="glyphicon glyphicon-console" aria-hidden="true"></span> Contribute Code</td>
- <td>Read the <a href="{{< ref "how-to-contribute/contribute-code" >}}">Code Contribution Guide</a></td>
+ <td>Read the <a href="{{< relref "how-to-contribute/contribute-code" >}}">Code Contribution Guide</a></td>
</tr>
<tr>
<td><span class="glyphicon glyphicon-ok" aria-hidden="true"></span> Help With Code Reviews</td>
- <td>Read the <a href="{{< ref "how-to-contribute/reviewing-prs" >}}">Code Review Guide</a></td>
+ <td>Read the <a href="{{< relref "how-to-contribute/reviewing-prs" >}}">Code Review Guide</a></td>
</tr>
<tr>
<td><span class="glyphicon glyphicon-thumbs-up" aria-hidden="true"></span> Help Preparing a Release</td>
@@ -48,13 +48,13 @@ Apache Flink is developed by an open and friendly community. Everybody is cordia
</tr>
<tr>
<td><span class="glyphicon glyphicon-list-alt" aria-hidden="true"></span> Contribute Documentation</td>
- <td>Read the <a href="{{< ref "how-to-contribute/contribute-documentation" >}}">Documentation Contribution Guide</a></td>
+ <td>Read the <a href="{{< relref "how-to-contribute/contribute-documentation" >}}">Documentation Contribution Guide</a></td>
</tr>
<tr>
<td><span class="glyphicon glyphicon-user" aria-hidden="true"></span> Support Flink Users</td>
<td>
<ul class="contribute-card-list">
- <li>Reply to questions on the <a href="{{< ref "community" >}}#mailing-lists">user mailing list</a></li>
+ <li>Reply to questions on the <a href="{{< relref "community" >}}#mailing-lists">user mailing list</a></li>
<li>Reply to Flink related questions on <a href="https://stackoverflow.com/questions/tagged/apache-flink">Stack Overflow</a> with the <a href="https://stackoverflow.com/questions/tagged/apache-flink"><code style="background-color: #cee0ed; border-color: #cee0ed;">apache-flink</code></a>, <a href="https://stackoverflow.com/questions/tagged/flink-streaming"><code style="background-color: #cee0ed; border-color: #cee0ed;">flink-streaming</code></a> or <a href="https://stackoverflow [...]
<li>Check the latest issues in <a href="http://issues.apache.org/jira/browse/FLINK">Jira</a> for tickets which are actually user questions</li>
</ul>
@@ -62,21 +62,21 @@ Apache Flink is developed by an open and friendly community. Everybody is cordia
</tr>
<tr>
<td><span class="glyphicon glyphicon-blackboard" aria-hidden="true"></span> Improve The Website</td>
- <td>Read the <a href="{{< ref "how-to-contribute/improve-website" >}}">Website Contribution Guide</a></td>
+ <td>Read the <a href="{{< relref "how-to-contribute/improve-website" >}}">Website Contribution Guide</a></td>
</tr>
<tr>
<td><span class="glyphicon glyphicon-volume-up" aria-hidden="true"></span> Spread the Word About Flink</td>
<td>
<ul class="contribute-card-list">
<li>Organize or attend a <a href="https://www.meetup.com/topics/apache-flink/">Flink Meetup</a></li>
- <li>Contribute to the <a href="{{< ref "posts" >}}">Flink blog</a></li>
- <li>Share your conference, meetup or blog post on the <a href="{{< ref "community" >}}#mailing-lists">community@flink.apache.org mailing list</a>, or tweet about it, tagging the <a href="https://twitter.com/ApacheFlink">@ApacheFlink</a> handle.</li>
+ <li>Contribute to the <a href="{{< relref "posts" >}}">Flink blog</a></li>
+ <li>Share your conference, meetup or blog post on the <a href="{{< relref "community" >}}#mailing-lists">community@flink.apache.org mailing list</a>, or tweet about it, tagging the <a href="https://twitter.com/ApacheFlink">@ApacheFlink</a> handle.</li>
</ul>
</td>
</tr>
<tr>
<td colspan="2">
- <span class="glyphicon glyphicon-question-sign" aria-hidden="true"></span> Any other question? Reach out to the <a href="{{< ref "community" >}}#mailing-lists">dev@flink.apache.org mailing list</a> to get help!
+ <span class="glyphicon glyphicon-question-sign" aria-hidden="true"></span> Any other question? Reach out to the <a href="{{< relref "community" >}}#mailing-lists">dev@flink.apache.org mailing list</a> to get help!
</td>
</tr>
</tbody>
diff --git a/docs/content/how-to-contribute/reviewing-prs.md b/docs/content/how-to-contribute/reviewing-prs.md
index 29b93051a..c85cf6b46 100644
--- a/docs/content/how-to-contribute/reviewing-prs.md
+++ b/docs/content/how-to-contribute/reviewing-prs.md
@@ -19,7 +19,7 @@ Every review needs to check the following six aspects. **We encourage to check t
### 1. Is the Contribution Well-Described?
-Check whether the contribution is sufficiently well-described to support a good review. Trivial changes and fixes do not need a long description. If the implementation is exactly [according to a prior discussion on Jira or the development mainling list]({{< ref "how-to-contribute/contribute-code" >}}#consensus), only a short reference to that discussion is needed.
+Check whether the contribution is sufficiently well-described to support a good review. Trivial changes and fixes do not need a long description. If the implementation is exactly [according to a prior discussion on Jira or the development mainling list]({{< relref "how-to-contribute/contribute-code" >}}#consensus), only a short reference to that discussion is needed.
If the implementation is different from the agreed approach in the consensus discussion, a detailed description of the implementation is required for any further review of the contribution.
Any pull request that changes functionality or behavior needs to describe the big picture of these changes, so that reviews know what to look for (and don’t have to dig through the code to hopefully understand what the change does).
@@ -31,7 +31,7 @@ Any pull request that changes functionality or behavior needs to describe the bi
### 2. Is There Consensus that the Change or Feature Should Go into Flink?
-This question can be directly answered from the linked Jira issue. For pull requests that are created without prior consensus, a [discussion in Jira to seek consensus]({{< ref "how-to-contribute/contribute-code" >}}) will be needed.
+This question can be directly answered from the linked Jira issue. For pull requests that are created without prior consensus, a [discussion in Jira to seek consensus]({{< relref "how-to-contribute/contribute-code" >}}) will be needed.
For `[hotfix]` pull requests, consensus needs to be checked in the pull request.
@@ -78,7 +78,7 @@ This is the detailed code review of the actual changes, covering:
* Does the code avoid to introduce additional compiler warnings?
* If dependencies have been changed, were the NOTICE files updated?
-Code guidelines can be found in the [Flink Code Style and Quality Guide]({{< ref "how-to-contribute/code-style-and-quality-preamble" >}}).
+Code guidelines can be found in the [Flink Code Style and Quality Guide]({{< relref "how-to-contribute/code-style-and-quality-preamble" >}}).
----
@@ -86,4 +86,4 @@ Code guidelines can be found in the [Flink Code Style and Quality Guide]({{< ref
If the pull request introduces a new feature, the feature should be documented. The Flink community is maintaining both an English and a Chinese documentation. So both documentations should be updated. If you are not familiar with the Chinese language, please open a Jira assigned to the `chinese-translation` component for Chinese documentation translation and link it with current Jira issue. If you are familiar with Chinese language, you are encouraged to update both sides in one pull request.
-See more about how to [contribute documentation]({{< ref "how-to-contribute/contribute-documentation" >}}).
\ No newline at end of file
+See more about how to [contribute documentation]({{< relref "how-to-contribute/contribute-documentation" >}}).
\ No newline at end of file
diff --git a/docs/content/posts/2023-01-26-release-1.16.1.md b/docs/content/posts/2023-01-26-release-1.16.1.md
index 5250b2095..05092eccc 100644
--- a/docs/content/posts/2023-01-26-release-1.16.1.md
+++ b/docs/content/posts/2023-01-26-release-1.16.1.md
@@ -39,7 +39,7 @@ We highly recommend all users upgrade to Flink 1.16.1.
## Binaries
-You can find the binaries on the updated [Downloads page]({{< ref "downloads" >}}).
+You can find the binaries on the updated [Downloads page]({{< relref "downloads" >}}).
## Docker Images
diff --git a/docs/content/powered-by.md b/docs/content/powered-by.md
index c63e25676..bfb789ea6 100644
--- a/docs/content/powered-by.md
+++ b/docs/content/powered-by.md
@@ -271,6 +271,6 @@ Apache Flink powers business-critical applications in many companies and enterpr
More Flink users are listed in the <a href="https://cwiki.apache.org/confluence/display/FLINK/Powered+by+Flink" target='_blank'><small><span class="glyphicon glyphicon-new-window"></span></small> Powered by Flink directory</a> in the project wiki. Please note that the list is *not* comprehensive. We only add users that explicitly ask to be listed.
-If you would you like to be included on this page, please reach out to the [Flink user mailing list]({{< ref "community" >}}) and let us know.
+If you would you like to be included on this page, please reach out to the [Flink user mailing list]({{< relref "community" >}}) and let us know.
{{< table_noheader "powered-by" >}}
diff --git a/docs/content/what-is-flink/flink-applications.md b/docs/content/what-is-flink/flink-applications.md
index dcee73d74..e59b90ad5 100644
--- a/docs/content/what-is-flink/flink-applications.md
+++ b/docs/content/what-is-flink/flink-applications.md
@@ -60,7 +60,7 @@ We briefly present each API, discuss its applications, and show a code example.
### The ProcessFunctions
-{{< docs_link file="flink-docs-stable/dev/stream/operators/process_function.html" name="ProcessFunctions">}} are the most expressive function interfaces that Flink offers. Flink provides ProcessFunctions to process individual events from one or two input streams or events that were grouped in a window. ProcessFunctions provide fine-grained control over time and state. A ProcessFunction can arbitrarily modify its state and register timers that will trigger a callback function in the futur [...]
+{{< docs_link file="flink-docs-stable/dev/stream/operators/process_function.html" name="ProcessFunctions">}} are the most expressive function interfaces that Flink offers. Flink provides ProcessFunctions to process individual events from one or two input streams or events that were grouped in a window. ProcessFunctions provide fine-grained control over time and state. A ProcessFunction can arbitrarily modify its state and register timers that will trigger a callback function in the futur [...]
The following example shows a `KeyedProcessFunction` that operates on a `KeyedStream` and matches `START` and `END` events. When a `START` event is received, the function remembers its timestamp in state and registers a timer in four hours. If an `END` event is received before the timer fires, the function computes the duration between `END` and `START` event, clears the state, and returns the value. Otherwise, the timer just fires and clears the state.
@@ -157,7 +157,7 @@ DataStream<Tuple2<String, Long>> result = clicks
Flink features two relational APIs, the {{< docs_link file="flink-docs-stable/dev/table/index.html" name="Table API and SQL">}}. Both APIs are unified APIs for batch and stream processing, i.e., queries are executed with the same semantics on unbounded, real-time streams or bounded, recorded streams and produce the same results. The Table API and SQL leverage [Apache Calcite](https://calcite.apache.org) for parsing, validation, and query optimization. They can be seamlessly integrated wi [...]
-Flink's relational APIs are designed to ease the definition of [data analytics]({{< ref "use-cases#analytics" >}}), [data pipelining, and ETL applications]({{< ref "use-cases#pipelines" >}}).
+Flink's relational APIs are designed to ease the definition of [data analytics]({{< relref "use-cases#analytics" >}}), [data pipelining, and ETL applications]({{< relref "use-cases#pipelines" >}}).
The following example shows the SQL query to sessionize a clickstream and count the number of clicks per session. This is the same use case as in the example of the DataStream API.
diff --git a/docs/content/what-is-flink/flink-architecture.md b/docs/content/what-is-flink/flink-architecture.md
index 6b2d83232..297cfeabd 100644
--- a/docs/content/what-is-flink/flink-architecture.md
+++ b/docs/content/what-is-flink/flink-architecture.md
@@ -24,7 +24,7 @@ Data can be processed as *unbounded* or *bounded* streams.
**Apache Flink excels at processing unbounded and bounded data sets.** Precise control of time and state enable Flink's runtime to run any kind of application on unbounded streams. Bounded streams are internally processed by algorithms and data structures that are specifically designed for fixed sized data sets, yielding excellent performance.
-Convince yourself by exploring the [use cases]({{< ref "use-cases" >}}) that have been built on top of Flink.
+Convince yourself by exploring the [use cases]({{< relref "use-cases" >}}) that have been built on top of Flink.
## Deploy Applications Anywhere
@@ -53,7 +53,7 @@ Flink features two deployment modes for applications, the *framework mode* and t
Flink is designed to run stateful streaming applications at any scale. Applications are parallelized into possibly thousands of tasks that are distributed and concurrently executed in a cluster. Therefore, an application can leverage virtually unlimited amounts of CPUs, main memory, disk and network IO. Moreover, Flink easily maintains very large application state. Its asynchronous and incremental checkpointing algorithm ensures minimal impact on processing latencies while guaranteeing e [...]
-[Users reported impressive scalability numbers]({{< ref "powered-by" >}}) for Flink applications running in their production environments, such as
+[Users reported impressive scalability numbers]({{< relref "powered-by" >}}) for Flink applications running in their production environments, such as
* applications processing **multiple trillions of events per day**,
* applications maintaining **multiple terabytes of state**, and