databird07 opened a new pull request, #20359: URL: https://github.com/apache/hudi/pull/20359
### Describe the issue this Pull Request addresses `TestHoodieDeltaStreamer` (~1860s) and `TestHoodieDeltaStreamerSchemaEvolutionQuick` (~410s) are the most expensive classes in hudi-utilities CI. Most of their cost is full-factorial parameter matrices whose rows repeat behaviour that other rows already cover. ### Summary and Changelog - `testLogicalTypesWithJsonSource`: 16 -> 8 rows, using an even-parity half fraction, so every pair of factor values still runs together. - `testCOWLogicalRepair` / `testMORLogicalRepair`: drop the v6/v8 "reconcile with verdict" rows. The reconcile path doesn't branch on table version and still runs on the current version. - `testUpsertsCOWContinuousMode`: drop SPARK x v8. v8 still runs with AVRO records, and all combinations still run on the current version. - SchemaEvolutionQuick: remove an exact duplicate MOR row, halve `testReorderingColumn` the same way, and remove one row that differs only in `rowWriterEnable`, which has no effect in these upsert-only tests. - No test bodies, waits or polling intervals change. Table versions 6, 8, 9 and 10 and both COW and MOR are still exercised. ### Impact Test-only. DeltaStreamer 198 -> 185 invocations (full class 1437s -> 1284s). SchemaEvolutionQuick 52 -> 39 invocations, median 268s -> 213s over 20 runs. JaCoCo shows no lost lines at class level. Measured locally on JDK 17 with 4 pinned CPUs and JaCoCo on; full numbers are in the commit message. ### Risk Level low. Only parameter rows are removed. The one tradeoff (no Spark-record StreamSync write to a v8 table) is called out in the commit message. ### Documentation Update none ### Contributor's checklist - [x] Read through [contributor's guide](https://hudi.apache.org/contribute/how-to-contribute) - [x] Enough context is provided in the sections above - [x] Adequate tests were added if applicable -- 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]
