Skip to content

Conversation

@github-actions
Copy link
Contributor

Cherry-picked from #59101

…59101)

### What problem does this PR solve?

The cache should be erased after compaction.

During compaction, segment data files are renamed. The renamed files may
hit the footer cache of the previous files (since the cache key is
composed of the file path and file size), so these caches need to be
invalidated.

Related PR: #xxx

Problem Summary:

### Release note

None

### Check List (For Author)

- Test <!-- At least one of them must be included. -->
    - [ ] 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 <!-- Add your reason?  -->

- Behavior changed:
    - [ ] No.
    - [ ] Yes. <!-- Explain the behavior change -->

- Does this need documentation?
    - [ ] No.
- [ ] Yes. <!-- Add document PR link here. eg:
apache/doris-website#1214 -->

### Check List (For Reviewer who merge this PR)

- [ ] Confirm the release note
- [ ] Confirm test cases
- [ ] Confirm document
- [ ] Add branch pick label <!-- Add branch pick label that this PR
should merge into -->
@github-actions github-actions bot requested a review from yiguolei as a code owner December 19, 2025 02:22
@Thearas
Copy link
Contributor

Thearas commented Dec 19, 2025

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?

@dataroaring dataroaring reopened this Dec 19, 2025
@Thearas
Copy link
Contributor

Thearas commented Dec 19, 2025

run buildall

@hello-stephen
Copy link
Contributor

BE UT Coverage Report

Increment line coverage 92.21% (71/77) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 53.15% (18451/34718)
Line Coverage 38.85% (170091/437760)
Region Coverage 33.63% (131456/390890)
Branch Coverage 34.54% (56758/164324)

@yiguolei
Copy link
Contributor

skip buildall

@github-actions github-actions bot added the approved Indicates a PR has been approved by one committer. label Dec 19, 2025
@github-actions
Copy link
Contributor Author

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

@github-actions
Copy link
Contributor Author

PR approved by anyone and no changes requested.

@yiguolei yiguolei merged commit 1aa4dc5 into branch-4.0 Dec 19, 2025
26 of 28 checks passed
@github-actions github-actions bot deleted the auto-pick-59101-branch-4.0 branch December 19, 2025 06:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by one committer. reviewed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants