diqiu50 opened a new issue, #13141: URL: https://github.com/apache/gravitino/issues/13141
### Version main branch ### Describe what's wrong The Trino integration workflow only runs the SQL-file harness (`trino_integration_test.sh` -> `:trino-connector:integration-test:TrinoTest`). No step runs `:trino-connector:integration-test:test`, so the JUnit ITs in that source set, including `TrinoUDFIT`, have never executed. `TrinoUDFIT` asserts exactly the behaviour that is broken (SHOW FUNCTIONS and invocation of a registered SQL function) and would have failed on its first run. It also waits for `show catalogs` to contain `<metalake>.<catalog>`, which never appears because the IT environment runs the connector in single-metalake mode. The unit tests in `TestGravitinoMetadataFunction` pass only because they assert that `LanguageFunction::sql` comes back byte-for-byte as stored, i.e. they assert the pass-through that is the defect. ### Error message and/or stacktrace N/A ### How to reproduce Run `./gradlew :trino-connector:integration-test:test -PskipDockerTests=false` locally: `TrinoUDFIT` fails with `Catalog gt_hive_udf sync timeout`. ### Additional context The JUnit ITs should run in the Trino integration workflow alongside the existing harness. -- 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]
