Skip to content

[refactor](cloud) Rename cloud compute group metadata class (#65817) - #66174

Open
deardeng wants to merge 1 commit into
apache:branch-4.0from
deardeng:codex/pick-65817-to-branch-4.0
Open

[refactor](cloud) Rename cloud compute group metadata class (#65817)#66174
deardeng wants to merge 1 commit into
apache:branch-4.0from
deardeng:codex/pick-65817-to-branch-4.0

Conversation

@deardeng

Copy link
Copy Markdown
Contributor

pick from #65817
Problem Summary: The FE cloud catalog metadata entity shared the ComputeGroup class name with the resource routing abstraction, making imports and usages ambiguous. Rename the cloud metadata entity to CloudComputeGroupMeta and update all production and unit-test references without changing runtime behavior or persisted metadata.

(cherry picked from commit a9816fa)

What problem does this PR solve?

Issue Number: close #xxx

Related PR: #xxx

Problem Summary:

Release note

None

Check List (For Author)

  • Test

    • Regression test
    • Unit Test
    • Manual test (add detailed scripts or steps below)
    • No need to test or manual test. Explain why:
      • This is a refactor/code format and no logic has been changed.
      • Previous test can cover this change.
      • No code files have been changed.
      • Other reason
  • Behavior changed:

    • No.
    • Yes.
  • Does this need documentation?

    • No.
    • Yes.

Check List (For Reviewer who merge this PR)

  • Confirm the release note
  • Confirm test cases
  • Confirm document
  • Add branch pick label

…5817)

Problem Summary: The FE cloud catalog metadata entity shared the
ComputeGroup class name with the resource routing abstraction, making
imports and usages ambiguous. Rename the cloud metadata entity to
CloudComputeGroupMeta and update all production and unit-test references
without changing runtime behavior or persisted metadata.

(cherry picked from commit a9816fa)
@deardeng
deardeng requested a review from morningman as a code owner July 28, 2026 11:22
@hello-stephen

Copy link
Copy Markdown
Contributor

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?

@deardeng

Copy link
Copy Markdown
Contributor Author

run buildall

@hello-stephen

Copy link
Copy Markdown
Contributor

FE UT Coverage Report

Increment line coverage 66.67% (20/30) 🎉
Increment coverage report
Complete coverage report

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.

2 participants