Skip to content

branch-4.1: [fix](auto partition) keep load row metrics monotonic for auto partition #64109 - #64136

Merged
yiguolei merged 1 commit into
branch-4.1from
auto-pick-64109-branch-4.1
Jun 8, 2026
Merged

branch-4.1: [fix](auto partition) keep load row metrics monotonic for auto partition #64109#64136
yiguolei merged 1 commit into
branch-4.1from
auto-pick-64109-branch-4.1

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Cherry-picked from #64109

…ion (#64109)
### What problem does this PR solve?
When loading into an auto partition table, BE may temporarily batch rows
whose target partitions do not exist yet. The previous logic first
incremented `doris_be_load_rows` when receiving the input block, then
decremented it when those rows were moved into the auto-partition
batching block, and finally incremented it again when the batched rows
were replayed after partition creation.
Because `doris_be_load_rows` is exposed as a counter, the negative
adjustment made the metric non-monotonic and could show row count drops
during auto partition loads.
This PR keeps the existing `RuntimeState` row compensation logic
unchanged, but stops applying negative deltas to the global BE load
row/byte metrics. It also skips global metric increments when replaying
the internal batched block, so each source row is counted once.
@github-actions
github-actionsBot requested a review from yiguolei as a code ownerJune 5, 2026 06:17
@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

@yiguolei

Copy link
Copy Markdown
Contributor

skip buildall

@yiguoleiyiguolei closed this Jun 8, 2026
@yiguoleiyiguolei reopened this Jun 8, 2026
@github-actionsgithub-actionsBot added the approved Indicates a PR has been approved by one committer. label Jun 8, 2026
@github-actions

Copy link
Copy Markdown
ContributorAuthor

PR approved by at least one committer and no changes requested.

@github-actions

Copy link
Copy Markdown
ContributorAuthor

PR approved by anyone and no changes requested.

@yiguolei
yiguolei merged commit 899ecd5 into branch-4.1Jun 8, 2026
32 of 34 checks passed
@morningman
morningman deleted the auto-pick-64109-branch-4.1 branch July 8, 2026 14:10
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approvedIndicates a PR has been approved by one committer.reviewed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@hello-stephen@yiguolei@sollhui