docs(blog): minor update on 2025 Hudi blog#17753
Merged
xushiyan merged 1 commit intoapache:asf-sitefrom Dec 30, 2025
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
This PR makes minor wording improvements to the Apache Hudi 2025 year-in-review blog post. The changes enhance clarity and precision by improving tense consistency, removing redundant words, and correcting terminology.
- Improved tense consistency ("was" → "has been")
- Removed redundant descriptors ("growing", "expanding")
- Updated PMC terminology from "joined" to "was elected to"
- Improved sentence structure for better readability
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| Performance saw major gains across the board. Parquet binary copy for clustering delivered 10-15x faster execution with 95% compute reduction. Apache Flink writer achieved 2-3x improved throughput with Avro conversion eliminated in the write path. Apache Spark metadata-table streaming ran ~18% faster for update-heavy workloads. Indexing enhancements — partitioned record index, partition-level bucket index, HFile caching, and Bloom filters — delivered up to 4x speedup for lookups on massive tables. | ||
|
|
||
| Spark 4.0 and Flink 2.0 support were added. [Apache Polaris (Incubating)](https://polaris.apache.org/) catalog integration enabled multi-engine queries with unified governance. Operational simplicity improved with storage-based locking that eliminated external dependencies. New merge modes replaced legacy payload classes with declarative options, and SQL procedures enhanced table management directly in Spark SQL. See more details in the [release blog](https://hudi.apache.org/blog/2025/11/25/apache-hudi-release-1-1-announcement/). | ||
| Spark 4.0 and Flink 2.0 support was added. [Apache Polaris (Incubating)](https://polaris.apache.org/) catalog integration enabled multi-engine queries with unified governance. Operational simplicity improved with storage-based locking that eliminated external dependencies. New merge modes replaced legacy payload classes with declarative options, and SQL procedures enhanced table management directly in Spark SQL. See more details in the [release blog](https://hudi.apache.org/blog/2025/11/25/apache-hudi-release-1-1-announcement/). |
There was a problem hiding this comment.
The change from "were added" to "was added" may be grammatically incorrect. The subject "Spark 4.0 and Flink 2.0 support" is compound (two items), which typically takes a plural verb form. "were added" would be the grammatically correct choice unless the phrase is intended to refer to a single unified support feature.
Suggested change
| Spark 4.0 and Flink 2.0 support was added. [Apache Polaris (Incubating)](https://polaris.apache.org/) catalog integration enabled multi-engine queries with unified governance. Operational simplicity improved with storage-based locking that eliminated external dependencies. New merge modes replaced legacy payload classes with declarative options, and SQL procedures enhanced table management directly in Spark SQL. See more details in the [release blog](https://hudi.apache.org/blog/2025/11/25/apache-hudi-release-1-1-announcement/). | |
| Spark 4.0 and Flink 2.0 support were added. [Apache Polaris (Incubating)](https://polaris.apache.org/) catalog integration enabled multi-engine queries with unified governance. Operational simplicity improved with storage-based locking that eliminated external dependencies. New merge modes replaced legacy payload classes with declarative options, and SQL procedures enhanced table management directly in Spark SQL. See more details in the [release blog](https://hudi.apache.org/blog/2025/11/25/apache-hudi-release-1-1-announcement/). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Minor wording update