Site: Add blog post for iceberg-rust 0.10.0#17032
Conversation
|
This is currently in draft as the release candidate voting is ongoing. @CTTY can you provide a review? |
89b4986 to
1735336
Compare
|
|
||
| ## Release Highlights | ||
|
|
||
| There has been plenty of contributions across the `iceberg-rust` library, here's a highlight of a few. |
There was a problem hiding this comment.
| There has been plenty of contributions across the `iceberg-rust` library, here's a highlight of a few. | |
| There have been plenty of contributions across the `iceberg-rust` library; here's a highlight of a few. |
mbutrovich
left a comment
There was a problem hiding this comment.
Just minor nits on a first pass. Thanks @dannycjones!
dannycjones
left a comment
There was a problem hiding this comment.
Sorry all, this draft didn't meet the right bar. Thank you all for the feedback, I've done a much deeper review of the changes mentioned and have pushed an update.
CTTY
left a comment
There was a problem hiding this comment.
Thanks Danny for writing up the blog!
| Work is already underway on several features for upcoming releases: | ||
|
|
||
| - **Table encryption**: With the foundational encryption stack landed, the community is working toward end-to-end encrypted reads and writes | ||
| - **Additional commit types**: Support for `RewriteDataFiles`, `RowDelta`, and `Overwrite` commit operations |
There was a problem hiding this comment.
I think it's better to put
- **Transaction layer improvement**: We are working on adding the snapshot validation mechanism to detect write conflicts, laying the groundwork for future support of RewriteDataFiles, RowDelta, and Overwrite commit operations.
There was a problem hiding this comment.
Thanks, that sets better expectations!
|
|
||
| ### Writer Improvements | ||
|
|
||
| - **Content-defined chunking** ([#2375](https://github.com/apache/iceberg-rust/pull/2375), [#2561](https://github.com/apache/iceberg-rust/pull/2561)): CDC table properties are now respected for optimizing Parquet file boundaries |
There was a problem hiding this comment.
- **Content-defined chunking(CDC)**
This is more explicit, I keep thinking about change data capture when seeing "CDC" :D
There was a problem hiding this comment.
I've opted to just spell it out for clarity in the new commit (about to push)
|
|
||
| ### Custom Runtime Support | ||
|
|
||
| The [`Runtime` trait](https://github.com/apache/iceberg-rust/pull/2308) can now be injected into catalogs, decoupling `iceberg-rust` from a hard tokio dependency at the catalog layer. This enables embedding in applications with custom async runtimes. |
There was a problem hiding this comment.
decoupling
iceberg-rustfrom a hard tokio dependency at the catalog layer. This enables embedding in applications with custom async runtimes.
This is inaccurate, Runtime is still a struct in iceberg-rust. users can now inject a customized tokio Runtime using the runtime api, but they cannot easily plug in a customized non-tokio runtime
There was a problem hiding this comment.
Thanks for calling this out, totally misunderstood.
I'm going to update it something like this:
This allows for injecting a customized Tokio runtime into the session.
For example, it is now possible to configure the thread stack size or maximum number of threads.
|
|
||
| - **Table encryption**: With the foundational encryption stack landed, the community is working toward end-to-end encrypted reads and writes | ||
| - **Additional commit types**: Support for `RewriteDataFiles`, `RowDelta`, and `Overwrite` commit operations | ||
| - **Extensibility**: Continued investment in abstractions for pluggable storage backends and runtime configuration |
There was a problem hiding this comment.
I'll remove it for now. What I had in mind was further storage trait work, such as extending to object_store. That being said, the work hasn't started so I'll omit it for this post.
This blog post announces the 0.10.0 release of iceberg-rust.
The content is an AI-assisted summary. I've reviewed the content and adjusted some items that were misleading.
I've generated the blog locally and reviewed that everything renders OK.