[website] Release 0.8 blog post and update Download page #1868
Conversation
website/blog/releases/0.8.md
Outdated
| @@ -0,0 +1,192 @@ | |||
| --- | |||
| title: "Apache Fluss 0.8: Streaming Lakehouse with Iceberg/Lance" | |||
There was a problem hiding this comment.
Add Announcing in title will be more precise for an announcement, how about: Announcing Apache Fluss 0.8: Streaming Lakehouse for AI & Analytics ?
There was a problem hiding this comment.
++1 for (AI & Analytics)
| Apache Fluss is now fully compatible with **Apache Flink 2.1**, ensuring seamless integration with the latest Flink runtime and APIs. | ||
| This update strengthens Fluss’s role as a unified streaming storage layer, providing reliable performance and consistency for modern data pipelines built on Flink. | ||
|
|
||
| ### Delta Join |
There was a problem hiding this comment.
The title feels that Delta Join is part of Fluss's key feature, but it is a feature of Apache Flink, and Fluss can be used as a streaming storage for flink streaming join. Maybe Delta Joins with Apache Flink is more proper ?
There was a problem hiding this comment.
Since this is listed under Flink 2.1, it is implicitly an integration feature with Flink. I’ll keep the title as is for conciseness. We’ve already noted, This release introduces support for Delta Joins with Apache Flink, so the context should be clear.
|
|
||
| TODO: add documentation link | ||
|
|
||
| ### Materialized Table |
There was a problem hiding this comment.
Materialized Table with Apache Flink
website/blog/releases/0.8.md
Outdated
| The Helm chart simplifies provisioning, upgrades, and scaling by packaging configuration, manifests, and dependencies into a single, versioned release. | ||
| This should help users running Fluss on Kubernetes faster, more reliably, and with easier integration into existing CI/CD and observability setups, significantly lowering the barrier for teams adopting Fluss in production. | ||
|
|
||
| TODO: add documentation link |
There was a problem hiding this comment.
nit, we'd address all TODOs before release.
website/blog/releases/0.8.md
Outdated
| ## Upgrade Notes | ||
|
|
||
| The Fluss community tries to ensure that upgrades are as seamless as possible. However, certain changes may require users to make adjustments to certain parts of the program when upgrading to version 0.8. | ||
| Please refer to the [upgrade notes](/docs/next/maintenance/operations/upgrade-notes-0.8/) for a comprehensive list of adjustments to make and issues to check during the upgrading process. |
There was a problem hiding this comment.
@wuchong I noticed an inconsistency in our Java version recommendations across the documentation:
Deployment Documentation:
deploying-distributed-cluster.mddeploying-local-cluster.md
Both recommend Java 17+ and explicitly state that "Java 8 and Java 11 are not recommended."
Upgrade Notes:
upgrade-notes-0.8.md
States: "We strongly recommend upgrading to Java 11 or higher" and "All Flink versions currently supported by Fluss are fully compatible with Java 11."
The Issue:
This creates conflicting guidance for users. Since Flink 1.18, 1.19, and 1.20 all fully support Java 17, and Java 17 is our recommended version in deployment docs, should we update the upgrade notes to also recommend Java 17 as the minimum/recommended version?
If there's a specific technical reason to keep Java 11 as the recommended version in upgrade notes, please let me know so we can update the deployment docs accordingly for consistency.
There was a problem hiding this comment.
Hi @MehulBatra, that's a great question.
The Deployment Documentation recommends Java 17+ for server deployments, while the Upgrade Notes mention the build-time language upgrade from Java 8 to Java 11.
In Fluss 0.7 and earlier, the distribution was built with Java 8 but recommended to be deployed on Java 17. Starting with Fluss 0.8, the distribution is now built with Java 11, while still recommending Java 17 for deployment.
This approach ensures Fluss remains compatible with Java 11 environments (e.g., many Flink clusters still run on Java 11 and require Fluss clients to be Java 11 compatible).
But I agree we may need to improve the word more clear about build language and deploy language.
wuchong
force-pushed
the
0.8-blog-and-download
branch
from
61807c0 to
cd0fcd7
Compare
|
Thank you all for the reviewing. I have addressed the comments and also update documentation for the missing parts. |
leonardBang
left a comment
leonardBang
left a comment
There was a problem hiding this comment.
Thanks @wuchong for the update, the updated PR looks good to me. Left one minor comments, feel free to address or not.
| > Alibaba-HZY, CaoZhen, CenterCode, CodeDrinks, David, Giannis Polyzos, Hemanth Savasere, Hongshun Wang, Jark Wu, Jensen, Junbo Wang, Kerwin, Leonard Xu, Liebing, Maggie Cao, Mahesh Sambaram, MehulBatra, Michael Koepf, Rafael Sousa, Rion Williams, Ron, Sergey Nuyanzin, SeungMin, Wang Cheng, XianmingZhou00, Xuyang, Yang Guo, Yang Wang, Yunchi Pang, ZijunZhao, Zmm, andybj0228, buvb, cxxwang, dependabot[bot], jackylee, leosanqing, naivedogger, ocean.wy, pisceslj, totalo, xiaochen, xiaozhou, xx789, yunhong, yuxia Luo | ||
|
|
||
| Apache Fluss is under active development. Be sure to stay updated on the project, give it a try and if you like it, | ||
| don’t forget to give it some ❤️ via ⭐ on [GitHub](https://github.com/apache/fluss). No newline at end of file |
There was a problem hiding this comment.
maybe the ending could be shorter like:
| don’t forget to give it some ❤️ via ⭐ on [GitHub](https://github.com/apache/fluss). | |
| give it a try and show your support with a ⭐ on [GitHub](https://github.com/apache/fluss). |
wuchong
force-pushed
the
0.8-blog-and-download
branch
from
485be4c to
d93c89b
Compare
4 participants
Purpose
Linked issue: close #xxx
Brief change log
Tests
API and Format
Documentation