shuke987 opened a new pull request, #65724:
URL: https://github.com/apache/doris/pull/65724

   ### What problem does this PR solve?
   
   Issue Number: N/A
   
   Related PR: #65536
   
   Problem Summary:
   
   Backport #65536 to branch-4.1. The affected unique-key MOW regression cases 
inspect historical physical rows, sequence values, skip bitmaps, or rowset 
versions. Background auto compaction can merge those rowsets before the 
physical-row assertion runs even though user-visible SQL results remain correct.
   
   This backport adds table-level `disable_auto_compaction=true` to the eight 
still-affected case files. `test_p_seq_publish_read_from_old.groovy` is 
intentionally omitted because branch-4.1 already contains the same protection 
from #64508.
   
   ### Release note
   
   None
   
   ### Check List (For Author)
   
   - Test
       - [x] Regression test
       - [ ] Unit Test
       - [ ] Manual test
       - [ ] No need to test or manual test.
   
     Validation:
     - The representative `test_flexible_partial_update_publish_conflict_seq` 
suite passed on an authorized branch-4.1 cluster during #65536 validation.
     - `git diff --check origin/branch-4.1...HEAD` passed.
     - The branch diff contains only the eight intended regression case files.
   
   - Behavior changed:
       - [x] No.
       - [ ] Yes.
   
   - Does this need documentation?
       - [x] No.
       - [ ] Yes.
   
   ### Check List (For Reviewer who merge this PR)
   
   - [ ] Confirm the release note
   - [ ] Confirm test cases
   - [ ] Confirm document
   - [ ] Add branch pick label
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to