build(deps): upgrade opendal from 0.57 to 0.58 - #6656
Open
Xuanwo wants to merge 2 commits into
Open
Conversation
OpenDAL 0.58 returns Operator from Operator::new directly (no finish()), and replaces HttpClientLayer with OperationContext + HttpTransporter for custom HTTP transports. Adapt the GCS storage backend and the HTTPS TLS regression test accordingly.
Xuanwo
marked this pull request as ready for review
August 4, 2026 09:13
Collaborator
|
Thank you @Xuanwo |
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.
Description
Upgrade Apache OpenDAL from 0.57 to 0.58.1 so Quickwit stays on the latest storage layer release (including GCS path encoding and HTTP transport fixes).
OpenDAL 0.58 has a few API changes that this PR adapts to:
Operator::new(...)now returnsResult<Operator>directly; the old.finish()step is gone.HttpClientLayer/raw::HttpClient. The HTTPS TLS regression test now injects a reqwest client throughOperationContext+HttpTransporter/ReqwestTransport.How was this PR tested?
cargo check -p quickwit-storage --features gcscargo test -p quickwit-storage --features gcs --lib(71 tests, includingtest_gcs_storage_get_slice_over_https_with_verified_tls)dd-rust-license-tool --config quickwit/license-tool.toml --manifest-path quickwit/Cargo.toml check