[feature](maxcompute)support maxcompute ram_role_arn and ecs_ram_role authenticate.#60649
[feature](maxcompute)support maxcompute ram_role_arn and ecs_ram_role authenticate.#60649morningman merged 3 commits intoapache:masterfrom
Conversation
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
|
run buildall |
Cloud UT Coverage ReportIncrement line coverage Increment coverage report
|
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
| Account account = new AliyunAccount(accessKey, secretKey); | ||
| return new Odps(account); | ||
| } else if (authType.equalsIgnoreCase(MCProperties.AUTH_TYPE_RAM_ROLE_ARN)) { | ||
| String accessKey = properties.get(MCProperties.ACCESS_KEY); |
There was a problem hiding this comment.
why we still need ak,sk for arn type?
There was a problem hiding this comment.
This is typically used to access maxcompute across Alibaba Cloud accounts, and aksk is required.
fe/fe-core/src/main/java/org/apache/doris/datasource/maxcompute/MaxComputeExternalTable.java
Outdated
Show resolved
Hide resolved
|
run buildall |
Cloud UT Coverage ReportIncrement line coverage Increment coverage report
|
|
run buildall |
Cloud UT Coverage ReportIncrement line coverage Increment coverage report
|
FE UT Coverage ReportIncrement line coverage |
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
|
run buildall |
Cloud UT Coverage ReportIncrement line coverage Increment coverage report
|
FE UT Coverage ReportIncrement line coverage |
TPC-H: Total hot run time: 28918 ms |
TPC-DS: Total hot run time: 183895 ms |
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
…from #60649 (#61717) ### What problem does this PR solve? Issue Number: N/A Related PR: #60649, #60905 Problem Summary: #60649 added support for MaxCompute `ram_role_arn` and `ecs_ram_role` authentication on `master`, and #60905 picked it to `branch-4.0`. `branch-4.1` is based on `branch-4.0`, but because the MaxCompute write path differs between branches, part of the write-side adaptation was not picked over. As a result, on `branch-4.1`, MaxCompute INSERT/write still relied on `access_key/secret_key` in some code paths, and could not correctly reuse the catalog `properties` for `ram_role_arn` or `ecs_ram_role` authentication. This PR supplements the missing pick for `branch-4.1`.
What problem does this PR solve?
Problem Summary:
support maxcompute RAMRoleArn and ECSRAMRole authenticate, not only ak-sk.
can ref : https://www.alibabacloud.com/help/zh/maxcompute/user-guide/configure-access-credentials#599325c7000vc
method 3 & 4.
Release note
support maxcompute RAMRoleArn and ECSRAMRole authenticate, not only ak-sk.
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
[catalog](maxcompute)add maxcompute catalog auth properties. doris-website#3491
Check List (For Reviewer who merge this PR)