Skip to content

branch-4.0: [fix](load) respect profile level for writer details #64620#64710

Open
github-actions[bot] wants to merge 1 commit into
branch-4.0from
auto-pick-64620-branch-4.0
Open

branch-4.0: [fix](load) respect profile level for writer details #64620#64710
github-actions[bot] wants to merge 1 commit into
branch-4.0from
auto-pick-64620-branch-4.0

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Cherry-picked from #64620

### What problem does this PR solve?

PR #64349 removed the stored RuntimeState from shared DeltaWriterV2 to
fix a valid lifetime issue. However, the master change did not move the
existing detailed-writer-profile gate to the VTabletWriterV2 call site.
As a result, closing tablet writer v2 always passed the operator profile
into DeltaWriterV2Map, and DeltaWriterV2/MemTableWriter detailed child
profiles were still emitted even when profile_level was 1. Pass the
profile only when profile_level is at least 2 so level 1 keeps only
merged profile counters as intended.
@github-actions github-actions Bot requested a review from morningman as a code owner June 22, 2026 15:47
@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?

@hello-stephen

Copy link
Copy Markdown
Contributor

run buildall

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