fix(storage): initialize OpenDAL's default HTTP transport - #6678
Merged
Conversation
OpenDAL 0.58 no longer auto-installs the Reqwest transport when default features are disabled, causing GCS requests to fail before reaching the backend. Use the canonical transport feature and initialize the default explicitly. Closes #6677
guilload
approved these changes
Aug 11, 2026
Member
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
2 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
OpenDAL 0.58 moved HTTP handling behind a process-wide transport. Quickwit disables OpenDAL's default features, including
auto-register-services, so the migration in #6656 left normal GCS operators with a lazy default transport but no installed implementation. The first GCS request therefore failed withConfigInvalid: default HTTP transport is not installed.This PR:
opendal::install_default()at the shared GCS constructor so the compiled Reqwest transport is registered as OpenDAL's process-wide default before the first GCS requestreqwest-rustls-tlsalias with the canonicalhttp-transport-reqwestfeature. Both select the same Reqwest/Rustls transport in OpenDAL 0.58 butreqwest-rustls-tlswill be deleted in 0.59How was this PR tested?
This issue was discovered while following the local development instructions in
CONTRIBUTING.mdand runningmake test-all. Before the fix, the GCS integration test consistently failed withConfigInvalid: default HTTP transport is not installed.After the fix:
full suite.
make test-allpassed 3,030 tests with 17 skipped; the 10 failpointtests also passed.
Closes #6677