diqiu50 opened a new issue, #10454:
URL: https://github.com/apache/gravitino/issues/10454
### Describe the feature
Add automated multi-version integration testing for the Trino connector,
covering Trino versions 435–478 through a manually-triggered GitHub Actions
workflow.
### Motivation
The Gravitino Trino connector supports multiple Trino version ranges
(435-439, 440-445, 446-451, 452-468, 469-472, 473-478). Currently there is no
automated way to verify compatibility across all these versions. Manually
testing each version is error-prone and time-consuming.
### Describe the solution
1. Add three incremental patch files to downgrade test resources from the
latest Trino version to older versions:
- `trino-478-473.patch`: adjusts SQL/expected outputs for Trino ≤473
- `trino-473-452.patch`: adds JVM diagnostics and Iceberg test
adjustments for Trino ≤452
- `trino-452-446.patch`: removes JVM config and adjusts column properties
for Trino ≤446
2. Enhance `trino_integration_test.sh` with `--auto_patch` and
`--trino_version` parameters that automatically apply the appropriate patches
before testing and restore files afterward (using `trap EXIT` for robustness).
3. Add `.github/workflows/trino-multi-version-test.yml`: a
manually-triggered workflow with 7 explicit steps (one per Trino version: 478,
473, 469, 452, 446, 440, 435), each directly invoking
`trino_integration_test.sh` with the correct connector module.
--
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]
