[flink-training] branch master updated: [hotfix] Fix links to old documentation

[nk...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

nkruber pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/flink-training.git


The following commit(s) were added to refs/heads/master by this push:
     new e9e5adf  [hotfix] Fix links to old documentation
e9e5adf is described below

commit e9e5adfab00e20335142fbf3a6603db16f396432
Author: Ali Bahadir Zeybek <al...@ververica.com>
AuthorDate: Thu Oct 21 15:56:30 2021 +0200

    [hotfix] Fix links to old documentation
---
 README.md                      | 2 +-
 hourly-tips/README.md          | 4 ++--
 long-ride-alerts/DISCUSSION.md | 2 +-
 long-ride-alerts/README.md     | 4 ++--
 ride-cleansing/README.md       | 4 ++--
 rides-and-fares/README.md      | 2 +-
 6 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/README.md b/README.md
index 34ded7b..0fc84e1 100644
--- a/README.md
+++ b/README.md
@@ -132,7 +132,7 @@ Then you should be able to open [`RideCleansingTest`](ride-cleansing/src/test/ja
 
 > **:information_source: Note for Scala users:** You will need to use IntelliJ with the JetBrains Scala plugin, and you will need to add a Scala 2.12 SDK to the Global Libraries section of the Project Structure as well as to the module you are working on.
 > IntelliJ will ask you for the latter when you open a Scala file.
-> Please note that Scala 2.12.8 and above are not supported (see [Flink Scala Versions](https://ci.apache.org/projects/flink/flink-docs-stable/docs/dev/datastream/project-configuration/#scala-versions for details))!
+> Please note that Scala 2.12.8 and above are not supported (see [Flink Scala Versions](https://nightlies.apache.org/flink/flink-docs-stable/docs/dev/datastream/project-configuration/#scala-versions for details))!
 
 ## Use the taxi data streams
 
diff --git a/hourly-tips/README.md b/hourly-tips/README.md
index 142edec..a49a4c5 100644
--- a/hourly-tips/README.md
+++ b/hourly-tips/README.md
@@ -59,8 +59,8 @@ Note that it is possible to cascade one set of time windows after another, so lo
 
 ## Documentation
 
-- [Windows](https://ci.apache.org/projects/flink/flink-docs-stable/dev/stream/operators/windows.html)
-- [See the section on aggregations on windows](https://ci.apache.org/projects/flink/flink-docs-stable/dev/stream/operators/#datastream-transformations)
+- [Windows](https://nightlies.apache.org/flink/flink-docs-stable/docs/dev/datastream/operators/windows)
+- [See the section on aggregations on windows](https://nightlies.apache.org/flink/flink-docs-stable/docs/dev/datastream/operators/overview/#datastream-transformations)
 
 ## Reference Solutions
 
diff --git a/long-ride-alerts/DISCUSSION.md b/long-ride-alerts/DISCUSSION.md
index a91e7fc..143b5e2 100644
--- a/long-ride-alerts/DISCUSSION.md
+++ b/long-ride-alerts/DISCUSSION.md
@@ -31,7 +31,7 @@ These cases are worth noting:
 event will be stored in state indefinitely (this is another leak!).
 
 These leaks could be addressed by either
-using [state TTL](https://ci.apache.org/projects/flink/flink-docs-stable/dev/stream/state/state.html#state-time-to-live-ttl),
+using [state TTL](https://nightlies.apache.org/flink/flink-docs-stable/docs/dev/datastream/fault-tolerance/state/#state-time-to-live-ttl),
 or another timer, to eventually clear any lingering state.
 
 ### Bottom line
diff --git a/long-ride-alerts/README.md b/long-ride-alerts/README.md
index b95e261..07bc566 100644
--- a/long-ride-alerts/README.md
+++ b/long-ride-alerts/README.md
@@ -76,8 +76,8 @@ The challenge is figuring out what state and timers to use, and when to set and
 
 ## Documentation
 
-- [ProcessFunction](https://ci.apache.org/projects/flink/flink-docs-stable/dev/stream/operators/process_function.html)
-- [Working with State](https://ci.apache.org/projects/flink/flink-docs-stable/dev/stream/state/index.html)
+- [ProcessFunction](https://nightlies.apache.org/flink/flink-docs-stable/docs/dev/datastream/operators/process_function)
+- [Working with State](https://nightlies.apache.org/flink/flink-docs-stable/docs/dev/datastream/fault-tolerance/state)
 
 ## After you've completed the exercise
 
diff --git a/ride-cleansing/README.md b/ride-cleansing/README.md
index ee76a47..254291b 100644
--- a/ride-cleansing/README.md
+++ b/ride-cleansing/README.md
@@ -80,8 +80,8 @@ Flink's DataStream API features a `DataStream.filter(FilterFunction)` transforma
 
 ## Documentation
 
-- [DataStream API](https://ci.apache.org/projects/flink/flink-docs-stable/dev/datastream_api.html)
-- [Flink JavaDocs](https://ci.apache.org/projects/flink/flink-docs-stable/api/java/)
+- [DataStream API](https://nightlies.apache.org/flink/flink-docs-stable/docs/dev/datastream/overview)
+- [Flink JavaDocs](https://nightlies.apache.org/flink/flink-docs-stable/api/java)
 
 ## Reference Solutions
 
diff --git a/rides-and-fares/README.md b/rides-and-fares/README.md
index b5ff381..2172513 100644
--- a/rides-and-fares/README.md
+++ b/rides-and-fares/README.md
@@ -77,7 +77,7 @@ For the purposes of this exercise it's okay to assume that the START and fare ev
 
 ## Documentation
 
-- [Working with State](https://ci.apache.org/projects/flink/flink-docs-stable/dev/stream/state/index.html)
+- [Working with State](https://nightlies.apache.org/flink/flink-docs-stable/docs/dev/datastream/fault-tolerance/state)
 
 ## Reference Solutions