Uh oh!
There was an error while loading. Please reload this page.
[feat](s3) support S3 storage vault credentials provider without role ARN - #64766
Conversation
hello-stephen
commented
Jun 24, 2026
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
sollhui
commented
Jun 24, 2026
run buildall |
sollhui
commented
Jun 24, 2026
/review |
There was a problem hiding this comment.
Summary:
I found three correctness issues in the provider-only S3 vault support. The CREATE/add path is partially covered, but related ALTER, SHOW CREATE, and recycler credential-provider paths are not complete.
Critical checkpoint conclusions:
- Goal/test proof: the PR aims to support S3 storage vault credential providers without a role ARN. The add path has tests, but ALTER, SHOW CREATE round-trip, and recycler v1 behavior are not covered.
- Scope/focus: the code change is small, but it misses parallel paths that consume the same vault credential state.
- Concurrency/lifecycle: no new concurrency or lifecycle hazard found in the changed code.
- Config/compatibility:
aws_credentials_provider_version=v1remains an accepted mutable config and behaves differently for the new provider-only state. - Tests/results: added tests validate provider-only ADD only; missing tests correspond to the inline findings.
- Observability/persistence/data correctness: persistence of the new state is explicit, but downstream consumers do not all serialize or honor it correctly.
Subagent conclusions:
optimizer-rewrite: OR-1 and OR-2 became inline comments M-1 and M-2; OR-3 was found during convergence and became M-3.tests-session-config: TSC-1 duplicated OR-1 and was merged into M-1.- Convergence round 2 ended with both subagents replying
NO_NEW_VALUABLE_FINDINGSfor the final M-1/M-2/M-3 comment set.
User focus: no additional user-provided review focus was present.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
PR approved by at least one committer and no changes requested. |
hello-stephen
commented
Jun 24, 2026
TPC-H: Total hot run time: 29374 ms |
hello-stephen
commented
Jun 24, 2026
TPC-DS: Total hot run time: 173728 ms |
hello-stephen
commented
Jun 24, 2026
ClickBench: Total hot run time: 25.29 s |
hello-stephen
commented
Jun 24, 2026
FE Regression Coverage ReportIncrement line coverage |
Uh oh!
There was an error while loading. Please reload this page.
### What problem does this PR solve? Issue Number: close #xxx Related PR: apache#64766 Problem Summary: The branch-4.0 backport left an unused CredProviderTypePB import in S3Properties.java, causing the FE Code Style Checker to fail. Remove the unused import. ### Release note None ### Check List (For Author) - Test: mvn clean checkstyle:check - Behavior changed: No - Does this need documentation: No
### What problem does this PR solve? Issue Number: close #xxx Related PR: apache#64766 Problem Summary: The branch-4.0 backport used provider enum values such as CONTAINER and ENV in Cloud and FE tests, but branch-4.0's Cloud proto only defines DEFAULT, SIMPLE, and INSTANCE_PROFILE. This caused Cloud UT to fail while compiling meta_service_test.cpp. Adapt the provider-only storage vault coverage to use INSTANCE_PROFILE and add the missing FE conversion helper and AWS_CREDENTIALS_PROVIDER_TYPE compatibility handling for branch-4.0. ### Release note None ### Check List (For Author) - Test: mvn clean checkstyle:check; ./run-fe-ut.sh --run org.apache.doris.datasource.property.storage.S3PropertiesTest - Behavior changed: No - Does this need documentation: No
What problem does this PR solve?
S3 storage vault creation only treated role ARN as the credential-provider path. When users configured
s3.credentials_provider_typewithouts3.role_arn, FE did not persist the provider type intoObjectStoreInfoPB, and Cloud meta-service still required AK/SK for the vault. The recycler also only read credential provider type inside the role ARN branch.This change allows S3 storage vaults to use an explicit credentials provider type without role ARN. FE now writes
cred_provider_typewhens3.credentials_provider_typeorAWS_CREDENTIALS_PROVIDER_TYPEis set, Cloud meta-service accepts credential-provider-based S3 vaults without AK/SK, and the recycler reads the provider type independently from role ARN.