chore(deps): align with current iceberg-rust revision - #21
Merged
Merged
Conversation
1 of 23 tasks
|
datafusion-contrib/datafusion-distributed#749 |
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
3 participants
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.
Which issue does this PR close?
None. This is a dependency update.
Rationale for this change
The published Iceberg 0.10.1 crates use Arrow 58, while this integration uses DataFusion 55 and Arrow 59. They also lack APIs used by this integration, so switching to the crates.io release does not compile. Until a compatible Iceberg release is published, consumers must use the same Iceberg Git revision as this integration: Cargo treats different Git revisions as distinct crate sources with incompatible Rust types. Updating both Iceberg dependencies together keeps that revision aligned.
What changes are included in this PR?
icebergandiceberg-catalog-restGit pins from665c64eto8cb2ade.Cargo.lockfor the new revision.What is the testing strategy for this PR?
No new tests are needed for this dependency-only change; the existing library tests exercise the integration against the updated dependencies. I ran
cargo check -p datafusion-icebergandcargo test -p datafusion-iceberg --lib(96 tests passed).Are there any user-facing changes?
There are no API or behavior changes intended. Consumers can align this integration with the updated
iceberg-rustrevision without carrying a second Iceberg Git revision.