Update iceberg and iceberg-catalog-rest to 0.9#1170
Merged
Conversation
michaeldjeffrey
approved these changes
Apr 7, 2026
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.
In iceberg 0.9.0, storage backend support (S3, GCS, local filesystem, etc.) has been moved to a separate iceberg-storage-opendal crate crates.io rather than being bundled directly into the iceberg crate behind feature flags.
This is a meaningful refactor. In earlier releases (0.7–0.8.x), opendal was a direct dependency of the iceberg crate itself, gated behind storage-s3, storage-gcs, storage-fs, etc. feature flags. The 0.9 work wired OpenDal with the Storage trait, with FileIO still using OpenDAL as the underlying implementation, but the goal is to make storage pluggable via the StorageFactory interface The Mail Archive.
Practical implications:
The iceberg crate itself no longer has opendal as a hard or feature-gated dep — it depends on the Storage trait abstraction instead.
If you want S3/GCS/local FS support, you now add iceberg-storage-opendal explicitly to your Cargo.toml alongside iceberg.
iceberg-catalog-rest (iceberg-rest-catalog in older naming) only depends on iceberg core and reqwest — it has never directly depended on opendal, so no change there.In iceberg 0.9.0, storage backend support (S3, GCS, local filesystem, etc.) has been moved to a separate iceberg-storage-opendal crate crates.io rather than being bundled directly into the iceberg crate behind feature flags.
This is a meaningful refactor. In earlier releases (0.7–0.8.x), opendal was a direct dependency of the iceberg crate itself, gated behind storage-s3, storage-gcs, storage-fs, etc. feature flags. The 0.9 work wired OpenDal with the Storage trait, with FileIO still using OpenDAL as the underlying implementation, but the goal is to make storage pluggable via the StorageFactory interface The Mail Archive.
Practical implications:
The iceberg crate itself no longer has opendal as a hard or feature-gated dep — it depends on the Storage trait abstraction instead.
If you want S3/GCS/local FS support, you now add iceberg-storage-opendal explicitly to your Cargo.toml alongside iceberg.
iceberg-catalog-rest (iceberg-rest-catalog in older naming) only depends on iceberg core and reqwest — it has never directly depended on opendal, so no change there.