nevzheng opened a new pull request, #14012: URL: https://github.com/apache/gravitino/pull/14012
### What changes were proposed in this pull request? - `TrinoCluster` starts the Trino stack (its own Hive, MySQL and PostgreSQL, workers, coordinator) through Testcontainers instead of `launch.sh` and docker compose, from the same `docker-script/init` files. Readiness checks replace polling and a fixed sleep; Ryuk cleans up. - `@TrinoFixture` starts lazily and reads the Gravitino server port from the test (`GravitinoServerAware`, implemented by `BaseIT`). - `TrinoQueryITBase` (also used by the Trino test tool) builds the cluster directly; the web UI `CatalogsPageTest` classes use the fixture. CI logs still land in `integration-test-common/build/trino-ci-container-log`. This PR includes the commits of the PRs below it. Review only its own commit: https://github.com/nevzheng/gravitino/compare/claude/13900-tc-07-dependencies-hive-variants...claude/13900-tc-08-trino-cluster ### Why are the changes needed? The Trino stack was the last container setup outside the framework, started by shell scripts with polling and a fixed sleep (design doc, Trino cluster). Part 6 of 6 of #14002. Fix: #14002 ### Does this PR introduce _any_ user-facing change? No. Test code only. ### How was this patch tested? Trino JUnit ITs and the Trino SQL test tool on Trino 478. **Stack:** STACKLINE -- 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]
