zkaoudi commented on code in PR #129:
URL: https://github.com/apache/wayang-website/pull/129#discussion_r3822725930
##########
blog/2026-08-20-gsoc-2026-datalake-friendly-wayang.md:
##########
@@ -0,0 +1,136 @@
+---
+slug: gsoc-2026-datalake-friendly-wayang
+title: "GSoC 2026: Making Apache Wayang More Datalake-Friendly"
+authors: [jun.wang]
+tags: [wayang, gsoc, trino, presto, bigquery, duckdb, parquet]
+---
+
+# GSoC 2026: Making Apache Wayang More Datalake-Friendly
+
+This blog post summarizes my Google Summer of Code 2026 project for Apache
Wayang. The original goal, "Make Wayang More Datalake-Friendly", was to
integrate modern analytical SQL engines and Parquet-based data sources into
Wayang's optimization and execution framework.
+
+Apache Wayang lets users describe a data-processing pipeline once and then
either choose an execution platform or let Wayang's optimizer decide where the
pipeline should run. This matters for modern analytical workloads because data
is often no longer stored inside a single database. It may live as Parquet
files in object storage, in federated catalogs queried by Trino or Presto, in a
serverless warehouse such as BigQuery, or in local analytical files processed
by DuckDB. The project focused on making these engines visible to Wayang as
execution platforms rather than treating them as separate external connectors.
+
+<div style={{textAlign: 'center'}}>
+ <img width="90%" alt="Apache Wayang data lake execution platforms project
overview" src="/img/blog/wayang-datalake/hero-image.png" />
Review Comment:
Can you change the "Plan" occurences in the image to "Query plan"? It can
seem ambiguous for someone reading for the first time
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
