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

   ## Proposed changes
   
   Relax the physical row-count sanity check in the unique-key-with-delete 
compaction cases:
   
   - `test_compaction_uniq_keys_with_delete.groovy`
   - `test_compaction_uniq_keys_with_delete_ck.groovy`
   
   Both cases still keep the final `qt_select_default3` query result check 
after cumulative compaction.
   
   ## Why
   
   Cloud P0 build `987265` failed in 
`compaction.test_compaction_uniq_keys_with_delete.test_compaction_uniq_keys_with_delete`:
   
   ```text
   assert (rowCount < 8 * replicaNum)
   8        |   8 1
            false
   ```
   
   The failing build already included the table-level 
`"disable_auto_compaction" = "true"` change from #65211. The build log shows 
cumulative compaction completed with `[OK]`, but the active rowsets can still 
contain exactly `8 * replicaNum` physical rows for this unique-key + delete 
scenario.
   
   The strict `<` check is therefore too strong for a physical intermediate 
state. `<=` keeps the guard that row count should not grow beyond the original 
inserted data volume, while leaving semantic correctness to the final query 
assertion.
   
   ## Validation
   
   - `git diff --check`
   - Inspected TeamCity build `987265` compressed build log:
     - table DDL includes `"disable_auto_compaction" = "true"`
     - cumulative compaction status is `[OK]`
     - active row-count sum is exactly `8`, matching `8 * replicaNum`
   
   Buildall will be requested after PR creation.
   
   ## Behavior changed
   
   No user-facing behavior change. Regression case deflake only.
   


-- 
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