-
Notifications
You must be signed in to change notification settings - Fork 3.7k
branch-3.1: [chore](param-refactor)Support independent AWS connection timeout settings for each object storage #54882 #54980
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
Conversation
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
…tings for each object storage (#54882) … ### What problem does this PR solve? Previously, connector properties such as use_path_style, connection.timeout, and request.timeout were shared across all object storage connectors. When multiple object storages (e.g., OSS, OBS, S3) were configured, their connection-related parameters could overwrite each other due to identical property names. After: Now, each object storage type supports prefixed property names to isolate configurations. For example: ``` # OSS-specific settings oss.connection.timeout=8000 oss.connection.request.timeout=15000 oss.use_path_style=true # OBS-specific settings obs.connection.timeout=12000 obs.connection.request.timeout=20000 obs.use_path_style=false ```
Contributor
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
Contributor
|
run buildall |
morrySnow
approved these changes
Aug 19, 2025
TPC-H: Total hot run time: 32712 ms |
TPC-DS: Total hot run time: 193222 ms |
ClickBench: Total hot run time: 29.01 s |
Contributor
FE UT Coverage ReportIncrement line coverage |
Member
|
run p0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Cherry-picked from #54882