manoj-ragupathy opened a new pull request, #13023: URL: https://github.com/apache/gluten/pull/13023
## What changes are proposed in this pull request? > **Stacked on #13020 → #13021 → #13022.** Targets `main`, so the diff currently also shows the earlier commits in the stack. **Only the top 2 commits belong to this PR** (3 new suite files + `VeloxTestSettings`). Draft until its parents merge. Final step of Spark 4.2.x support (#12569): widen coverage of the test module added in #13022. Spark 4.2.0 adds a set of "Enhanced" DSv2 filter suites that exercise the redesigned SPJ / runtime-filtering paths. Since those paths are exactly what the 4.2 shim had to rewrite (see the `BatchScanExecShim` rework and the `getCommonPartitionValues` caveat in #13021), they are the highest-value suites to run under Gluten rather than the ones most likely to already pass. | New suite | Tests | |---|---| | `GlutenDataSourceV2EnhancedPartitionFilterSuite` | 28 | | `GlutenDataSourceV2EnhancedRuntimePartitionFilterSuite` | 15 | | `GlutenDataSourceV2EnhancedDeleteFilterSuite` | 9 | | **Total** | **52** | Each is the standard 7-line wrapper — extends the upstream suite, mixes in `GlutenSQLTestsTrait` — and all three are registered in `VeloxTestSettings`. That registration is the part worth reviewing: a suite absent from it never runs at all. Part of #12569. ## How was this patch tested? ```bash ./build/mvn -Pspark-4.2 -Pscala-2.13 -Pjava-17 -Pbackends-velox -Pspark-ut test-compile -DskipTests ``` `BUILD SUCCESS`. I confirmed by reflection over the compiled classes that the three suites actually inherit 28 / 15 / 9 test cases, so they are genuinely running upstream's tests and not silently empty. **Same caveat as #13022:** these are compile-verified only — no `libgluten.so` locally — and they cannot run in CI until the image is rebuilt with the Spark 4.2 resources. I fully expect some of the 52 to need `excludeGlutenTest` / `ignore` entries once CI gives a real signal, and will follow up with those once the lanes are live. ## Was this patch authored or co-authored using generative AI tooling? Generated-by: GitHub Copilot CLI (Claude Opus 5) -- 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]
