From 8aa2a6a0cf3004b8510ad6589774fe88128ce9ad Mon Sep 17 00:00:00 2001 From: Chamikara Jayalath Date: Wed, 24 Sep 2025 09:34:42 -0700 Subject: [PATCH] Fix Managed I/O link in the blog --- .../www/site/content/en/blog/gsoc-25-yaml-user-accessibility.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/www/site/content/en/blog/gsoc-25-yaml-user-accessibility.md b/website/www/site/content/en/blog/gsoc-25-yaml-user-accessibility.md index 2c4704ee497d..b24661947ec7 100644 --- a/website/www/site/content/en/blog/gsoc-25-yaml-user-accessibility.md +++ b/website/www/site/content/en/blog/gsoc-25-yaml-user-accessibility.md @@ -27,7 +27,7 @@ limitations under the License. The relatively new Beam YAML SDK was introduced in the spirit of making data processing easy, but it has gained little adoption for complex ML tasks and hasn’t been widely used with -[Managed I/O](beam.apache.org/documentation/io/managed-io/) such as Kafka and Iceberg. +[Managed I/O](https://beam.apache.org/documentation/io/managed-io/) such as Kafka and Iceberg. As part of Google Summer of Code 2025, new illustrative, production-ready pipeline examples of ML use cases with Kafka and Iceberg data sources using the YAML SDK have been developed to address this adoption gap.