Skip to content

branch-4.1 [fix](fe) Fix simple aggregate cache after partition recycle#63530

Merged
yiguolei merged 2 commits into
apache:branch-4.1from
englefly:pick-63175-4.1
May 22, 2026
Merged

branch-4.1 [fix](fe) Fix simple aggregate cache after partition recycle#63530
yiguolei merged 2 commits into
apache:branch-4.1from
englefly:pick-63175-4.1

Conversation

@englefly
Copy link
Copy Markdown
Contributor

What problem does this PR solve?

pick #63175

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

englefly added 2 commits May 22, 2026 11:54
…63175)

Issue Number: None

Related PR: apache#61183

Problem Summary: Auto partition recycle updates table visible version
from the dynamic partition thread, while simple aggregate cache
validation reads the table visible version without holding the table
lock. Make table visible version fields visible across threads and
defensively invalidate simple aggregate cache on partition drop/replay
to avoid stale count(*) constants after partition recycle.
@englefly englefly changed the base branch from master to branch-4.1 May 22, 2026 07:55
@englefly englefly requested a review from yiguolei as a code owner May 22, 2026 07:55
@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?

@englefly
Copy link
Copy Markdown
Contributor Author

run buildall

@yiguolei
Copy link
Copy Markdown
Contributor

skip buildall

@yiguolei yiguolei merged commit 722d5a6 into apache:branch-4.1 May 22, 2026
32 of 34 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