8000 Return Non-Generic Errors from HttpStore by Rynoxx · Pull Request #366 · apache/arrow-rs-object-store · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Return Non-Generic Errors from HttpStore #366

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
May 17, 2025

Conversation

Rynoxx
Copy link
Contributor
@Rynoxx Rynoxx commented May 15, 2025

Which issue does this PR close?

Closes #365.

Rationale for this change

Allows for better error handling of HTTP statuses, and makes it consistent with how the S3/Azure/GCP clients handles RetryError.

What changes are included in this PR?

Adjust implementation of impl From<http::client::Error> for crate::Error to use RetryError::error when possible.

Are there any user-facing changes?

Most RetryError cases just returned crate::Error::GenericError before, now they'll return the crate::Error that matches the RetryError

… relevant crate::Error using RetryError::source.

Allows for better error handling of HTTP statuses, and makes it consistent with how the S3/Azure/GCP clients handles RetryError.
@Rynoxx Rynoxx force-pushed the align-retryerror-usage-http branch from 72f5d49 to 9f2a272 Compare May 16, 2025 14:00
@tustvold tustvold changed the title Adjust how RetryError is handled for http ObjectStore, convert to the relevant crate::Error using RetryError::source Return Non-Generic Errors from HttpStore May 17, 2025
@tustvold tustvold merged commit 407184a into apache:main May 17, 2025
8 checks passed
@Rynoxx Rynoxx deleted the align-retryerror-usage-http branch May 17, 2025 21:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Error handling of HTTP storage backend not utilizing retry::RetryError::error when possible
2 participants
0