nevzheng opened a new pull request, #14076: URL: https://github.com/apache/gravitino/pull/14076
### What changes were proposed in this pull request? - Kerberos tests change HDFS permissions and owners through one `KerberosHdfs` helper (keytab login, Hadoop `FileSystem`) instead of `hadoop fs` in the container. - Database grants and checks run over JDBC instead of `mysql -e` / `psql -c`. - LocalStack setup uses the AWS SDK, and its readiness waits on `/_localstack/health` instead of polling `awslocal`. - Kafka and Trino readiness ask the services directly (a Kafka API request; Trino's HTTP API) instead of running their CLIs. - `HudiCatalogKerberosHiveIT` drops two `hive -e` calls that never ran: the SQL was wrapped in literal quotes and the exit code was ignored, and the test asserts that the table does not exist. Left as they are: the `kadmin.local` scripts and keytab copies, and log collection, which run once per class or at close. This PR includes the commits of the PRs below it. Review only its own commit: https://github.com/nevzheng/gravitino/compare/claude/13900-tc-10-hive-jdbc...claude/13900-tc-11-no-cli ### Why are the changes needed? Each CLI call starts a JVM (or a Python CLI) in the container, and the old calls ignored exit codes, so a failed setup step went unnoticed. Locally (3 runs, medians, #14052 → this PR): the Kerberos fileset ITs 186 s → 167 s (−10 %), Paimon 67 s → 60 s (−10 %), Hudi 50 s → 43 s (−14 %), GVFS S3 117 s → 106 s (−9 %), the Kerberos Hive ITs 100 s → 92 s (−8 %); Iceberg, Iceberg REST, Kafka and Trino are flat. Fix: #14049 ### Does this PR introduce _any_ user-facing change? No. Test code only. ### How was this patch tested? Unit tests for the new helpers; the Kerberos fileset, Hive, Iceberg, Paimon and Hudi ITs, iceberg-rest-server Kerberos ITs, GVFS S3, Trino connector ITs and Kafka. **Stack:** … → #14052 → **#PR11** -- 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]
