Apache Iceberg Rust 0.10 revises table lifecycle and retention APIs

Apache Iceberg announced Rust 0.10 on July 21, adding table-maintenance capabilities and revising APIs around catalog removal and physical deletion. The release notes identify breaking changes that matter to applications embedding the Rust implementation.

Separate catalog removal from deletion

The release introduces snapshot-expiration work that respects the table’s history.expire settings and cleans associated statistics metadata. It also adds purge_table for deleting table metadata and data; some catalog implementations move deletion behavior from drop_table into that operation.

For maintainers, this is an API migration with a data-lifecycle consequence. Review every existing drop call and document whether the application intends to unregister a table, retain files for recovery, or delete them. A compile-time fix alone cannot answer that policy question.

Our assessment is that retention tests should begin with an explicit inventory: snapshots to retain, files expected to remain and the catalog entry’s intended state. Exercise the operation on disposable tables and compare that inventory afterward. Include failure recovery, because partially completed maintenance is where ambiguous ownership becomes expensive.

Budget for dependency and behavior changes

The release raises the minimum Rust version to 1.94 and moves to DataFusion 53 and Arrow 58. Its encryption work is foundational: encrypted writes remain explicitly blocked.

Application teams should therefore schedule the compiler and dependency updates alongside the catalog changes. A clean library build is only the first check; integration tests need to cover the application paths that read, overwrite and retire tables.

Keep encryption expectations separate from that upgrade decision. The presence of encryption-related internals does not establish a usable encrypted-write workflow. Evaluate the operations the release actually supports, and preserve that distinction in internal platform documentation.