danny0405 opened a new pull request, #20494: URL: https://github.com/apache/hudi/pull/20494
### Describe the issue this Pull Request addresses Part of #20405 and #20401 Phase 2 A3. Repeated materialized-view refresh needs real CLI/Connect coverage over Hudi and non-Hudi sources, including changes and removals rather than row counts alone. Depends on #20492's catalog reconciliation fix; #20423's append prerequisite is merged. ### Summary and Changelog - Add two materialized-view definitions over deterministic JSON and Hudi sources. - Run three refreshes through the actual Spark pipelines CLI, changing and removing source rows between runs. - Assert exact business-column contents for both views after every refresh. - Add local instructions and preserve generated definitions and client/server logs through the #20453 harness, supplied explicitly with --harness-dir. Validation: all three CLI refreshes and six exact-result checks passed on Spark Connect 4.1.1 / JDK 17 with master b0d16f94b3b plus #20492 (a940de6aaa1). Python syntax and git diff --check passed; description checked using scripts/pr_compliance.py. This PR does not claim the dependency has merged or CI has passed. ### Impact Test-only changes; no public API, storage format or runtime configuration changes. Uses today's purge truncate and full recomputation. No CI lane changes while #20453's CI shape remains under discussion. ### Risk Level low. Isolated local sources and targets, bounded client execution and harness-managed process cleanup. The test requires the catalog prerequisite in the candidate bundle. ### Documentation Update Add MATERIALIZED_VIEWS.md with commands, dependencies, expected data and Phase 2/4 boundaries. No website change is needed for developer test infrastructure. ### 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]
