danhuawang opened a new issue, #13068:
URL: https://github.com/apache/gravitino/issues/13068
### Version
main branch
### Describe what's wrong
The Trino multi-version integration test passes on Trino 478 and fails on
Trino 473.
On 473, `CREATE TABLE` against a Gravitino-backed Iceberg catalog succeeds.
The next statement, `SHOW CREATE TABLE`, fails. At the same time the Gravitino
Iceberg REST server logs `HTTP 404 Not Found`
(`javax.ws.rs.NotFoundException`). Trino 473's Iceberg REST client is calling
an endpoint that the current Iceberg REST service does not expose (previously
observed as token exchange hitting a missing `/v1/oauth/tokens` route).
This is a Trino 473 / Iceberg REST compatibility bug, not a CI workflow
misconfiguration.
### Error message and/or stacktrace
```text
Iceberg REST server error maybe caused by user request, response http
status: 404,
exception: class javax.ws.rs.NotFoundException, exception message: HTTP 404
Not Found
Execute sql in the tester lakehouse-iceberg/00000_create_table.sql under
catalog iceberg_mysql failed.
Sql:
show create table gt_db2.tb01;
```
Trino also fails to parse the REST error body:
```text
java.lang.IllegalArgumentException: Cannot parse to a string value: error:
{"message":"HTTP 404 Not Found","type":"NotFoundException","code":404,...}
```
### How to reproduce
1. Use current `main`.
2. Run the Trino multi-version workflow, or:
```bash
trino-connector/integration-test/trino-test-tools/trino_integration_test.sh \
--auto=all --auto_patch --trino_version=473 \
--trino_connector_dir=trino-connector/trino-connector-473-478/build/libs
```
3. Observe `Test Trino 478` pass and `Test Trino 473` fail on `SHOW CREATE
TABLE` after a successful `CREATE TABLE`.
Example run:
https://github.com/danhuawang/gravitino/actions/runs/34376085905/job/102549165242
### Additional context
Same class of failure as the enterprise Trino 473 Iceberg REST OAuth 404.
478 is fine on the same connector jar range (`trino-connector-473-478`).
--
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]
