diqiu50 opened a new pull request, #11909: URL: https://github.com/apache/gravitino/pull/11909
### What changes were proposed in this pull request? Add a `TEST_CONTAINERS` env var / `--test_containers` CLI option so Trino IT can start only the containers a test needs (e.g. `trino`+`mysql`) instead of the full stack. `TrinoITContainers` now exposes a generic `getServiceUrls()` map instead of fixed getters; `launch.sh`/`shutdown.sh`/`inspect_ip.sh` no longer assume the full container set; adds `docker-compose-trino-mysql.yaml` as the first subset; `trino_integration_test.sh` auto-maps `--test_set=jdbc-mysql` to `--test_containers=mysql`. ### Why are the changes needed? Trino IT always starts the full container stack even when a testset only needs one backend. Fix: #11907 ### Does this PR introduce _any_ user-facing change? Adds an optional `--test_containers` CLI flag / `TEST_CONTAINERS` env var; default (full stack) unchanged. ### How was this patch tested? Ran `trino_integration_test.sh` with default full-stack and mysql-only subset against `jdbc-mysql`. Manually verified launch/inspect/shutdown scripts clean up containers and networks correctly. -- 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]
