Skip to content

branch-4.1:[feature](maxcompute) supplement missing writer auth pick from #60649#61717

Open
hubgeter wants to merge 1 commit intoapache:branch-4.1from
hubgeter:pick_41_mc_auth_write
Open

branch-4.1:[feature](maxcompute) supplement missing writer auth pick from #60649#61717
hubgeter wants to merge 1 commit intoapache:branch-4.1from
hubgeter:pick_41_mc_auth_write

Conversation

@hubgeter
Copy link
Contributor

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.

@hubgeter hubgeter requested a review from yiguolei as a code owner March 25, 2026 08:53
@Thearas
Copy link
Contributor

Thearas commented Mar 25, 2026

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@hubgeter
Copy link
Contributor Author

run buildall

@hello-stephen
Copy link
Contributor

FE UT Coverage Report

Increment line coverage `` 🎉
Increment coverage report
Complete coverage report

@doris-robot
Copy link

BE UT Coverage Report

Increment line coverage 0.00% (0/1) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 52.85% (19591/37071)
Line Coverage 36.19% (182643/504739)
Region Coverage 32.49% (141068/434197)
Branch Coverage 33.71% (61944/183766)

@hello-stephen
Copy link
Contributor

BE Regression && UT Coverage Report

Increment line coverage 0.00% (0/1) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 69.51% (25217/36279)
Line Coverage 52.11% (262127/503026)
Region Coverage 49.53% (217037/438168)
Branch Coverage 50.86% (93725/184292)

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.

4 participants