Repository navigation
feat(storage-opendal): configurable retry policy via opendal.retry.* and s3.retry.* #3605
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
+283
−9
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
55bc5fb
feat(storage-opendal): read the s3.retry.* properties
emanuilov e61ef6e
feat(storage-opendal): add backend-independent opendal.retry.* proper…
emanuilov 96eb6fd
refactor(storage-opendal): keep the reviewed retry tests, add only th…
emanuilov 7048c0b
refactor(storage-opendal): resolve s3.retry.* overrides when building…
claude File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a reason we would put these in the s3 namespace and not in the new
opendalnamespace? It seems like these could apply to all opendal backends?Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I put them under s3. on purpose: they’re the same keys Iceberg Java’s S3FileIO uses (s3.retry.num-retries, s3.retry.min-wait-ms, s3.retry.max-wait-ms), so a catalog configuration written for Java works unchanged with iceberg-rust. They aren’t meant to be opendal-only: the object_store S3 backend (#3165) should read the same keys. To make that explicit, I can move the parsing into a small backend-neutral retry config in iceberg::io, which the opendal and object_store backends each turn into their own retry setup. Other schemes (GCS, Azure) could feed the same struct from their own keys later. Want me to do that in this PR?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That makes sense, wanting java configured tables to work out of the box makes sense but I wonder if we could layer these configs better. i.e have both namespaces available with the more specific one taking preference? Does something like that make sense?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just to check I understand: do you mean a generic set of retry keys in the opendal namespace that every OpenDAL backend uses, with s3.retry.* taking precedence for S3?
If so, here’s what I’d do:
Is that what you had in mind? If so, I’ll add it to this PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes! I think this makes sense to me!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pushed the change with the layered config: opendal.retry.* for every backend, with s3.retry.* overriding per key for S3.
Tested locally:
I didn’t reproduce real S3 throttling here, so which layer wins at runtime is covered by the unit tests rather than the e2e.