hello-stephen opened a new pull request, #69622: URL: https://github.com/apache/doris/pull/69622
## Problem The full compatibility passes `CompatibilityRunOriCase` and `CompatibilityRunDstCase` omit `-w`. The flexible fixture loaders preserve existing tables, but the tests only recognize `withOutLoadData` as a repeat execution. After initialization has written the final fixture, these passes repeat initialization DML: the downgrade fixture expects 10 but reads 999, and the upgrade fixture attempts to enable `UPDATE_FLEXIBLE_COLUMNS` again. This extends #69555 to those two exact phase names. Both row-store variants retain the existing complete final-row and feature-metadata assertions. Ordinary initialization, load scripts, DML, golden data and all assertions remain unchanged; existing persisted data is neither dropped nor reloaded. Related historical case issue: [DORIS-16977](http://39.106.86.136:8090/browse/DORIS-16977). Build 217636 reproduced both failures in each full compatibility phase. This is a test lifecycle fix, not a product correctness fix. ## Validation - Full original and modified test sources executed with mocked I/O: 60 checks on each of the exact 4.1.5 / 4.2.0-rc01 case archives' framework jars (Java 17 / Groovy 4.0.19). Checks cover unchanged initialization traces; rolling `-w`; both full phase names and row-store variants; repeated reads; rejection of corrupt, missing, additional rows and disabled feature metadata; and the actual loaders preserving existing tables. - All four real load/test sources compile and register through `GroovyFileSource`, `ScriptContext` and `SuiteScript` from both archived framework jars. The registration filter returns false before database execution. - A byte comparison confirms only the two entry conditions and adjacent comments change. `git diff --check` passes; independent static review completed. No database runtime rerun has been performed. The repeat branch validates persisted data and feature metadata; it does not add mixed-version DML coverage. This change does not fix the separate DDC downgrade failure or add post-downgrade test execution. Future validation requires case artifacts containing this fix on both sides and terminal phase-specific test evidence. -- 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]
