Skip to content

[fix](cloud) normalize SHOW PARTITIONS display for storage and replica (#60871) - #66057

Merged
yiguolei merged 1 commit into
apache:branch-4.1from
deardeng:codex/pick-60871-to-branch-4.1-master-merge-direct
Jul 29, 2026
Merged

[fix](cloud) normalize SHOW PARTITIONS display for storage and replica (#60871)#66057
yiguolei merged 1 commit into
apache:branch-4.1from
deardeng:codex/pick-60871-to-branch-4.1-master-merge-direct

Conversation

@deardeng

Copy link
Copy Markdown
Contributor

pick from #60871

In cloud mode, SHOW PARTITIONS now displays StorageMedium as OBJECT_STORAGE and ReplicaAllocation as . Also add PartitionsProcDirTest to cover cloud/non-cloud display behavior.

image

(cherry picked from commit 9688e57)

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

apache#60871)

In cloud mode, SHOW PARTITIONS now displays StorageMedium as
OBJECT_STORAGE and ReplicaAllocation as <null>. Also add
PartitionsProcDirTest to cover cloud/non-cloud display behavior.

<img width="462" height="312" alt="image"
src="https://github.com/user-attachments/assets/f5ac8ab8-3ffd-468c-a2ea-9a957e7e385a"
/>

(cherry picked from commit 9688e57)
@deardeng
deardeng requested a review from yiguolei as a code owner July 26, 2026 06:41
@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?

@yiguolei

Copy link
Copy Markdown
Contributor

run buildall

@hello-stephen

Copy link
Copy Markdown
Contributor

FE UT Coverage Report

Increment line coverage 15.38% (2/13) 🎉
Increment coverage report
Complete coverage report

@hello-stephen

Copy link
Copy Markdown
Contributor

FE Regression Coverage Report

Increment line coverage 100.00% (13/13) 🎉
Increment coverage report
Complete coverage report

@yiguolei
yiguolei merged commit 82f726e into apache:branch-4.1 Jul 29, 2026
29 of 32 checks passed
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.

3 participants