sinbad-io opened a new issue, #878: URL: https://github.com/apache/arrow-rs-object-store/issues/878
`parse_url_opts` selects the provider, applies configuration and returns the store with its decoded path. Cloud and HTTP builders accept `HttpConnector`, but the URL resolver cannot pass one through. A caller that needs a custom transport must duplicate provider dispatch or leave the URL resolver. This affects transport tracing, custom TLS and separate I/O runtimes. Add an optional connector to a new resolver entry point. Both resolver entry points use the existing provider dispatch. `None` keeps the default connector. Local and memory stores ignore the connector. Cloud and HTTP builders receive it through their existing `with_http_connector` methods. An implementation and focused tests are ready for review. It also forwards `HttpConnector` through `Arc<T>` so callers can share one connector across stores. This adds no dependency and changes no existing resolver result. AI assistance: an AI coding assistant wrote the code, tests and this draft text. The owner reviewed and approved the submitted text. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
