Gabriel39 opened a new pull request, #69112:
URL: https://github.com/apache/doris/pull/69112
### What problem does this PR solve?
When `enableTrinoJdbcTest=true`, `test_trino_timestamp_query_tvf` creates a
JDBC catalog pointing to `<docker-host>:8080`. The Iceberg stack runs Trino 482
but does not publish its container port, so FE fails the catalog connectivity
check with `Connection refused` before any timestamp query executes.
`test_trino_uuid_predicates` uses the same endpoint.
Publish `TRINO_JDBC_PORT:8080`, retaining the existing regression default of
8080 and allowing an override for shared hosts. Replace the
filesystem/CLI-presence health check with `SELECT 1`, so Compose `--wait` waits
for a query-ready server. Document the matching regression settings. The image
already supplies the required `memory` catalog.
### Release note
None
### Check List (For Author)
- Test:
- [x] Manual test: confirmed the original Compose configuration has no
published Trino port; checked default and overridden port mappings with `docker
compose config`.
- [x] Started an isolated Trino 482 service from the rendered
configuration and waited for its SQL health check to pass.
- [x] Connected through the published host port using the same Trino JDBC
435 driver as the suites. Verified `WITH SESSION` timestamp queries
with/without a CTE in UTC and Asia/Shanghai, and memory-catalog UUID inserts
plus equality, IN, range, BETWEEN and NULL predicates.
- Full Doris Groovy regressions were not run locally; the manual checks
cover fixture readiness, connectivity and remote SQL prerequisites.
- Behavior changed:
- [x] Yes: the test fixture publishes its configurable JDBC port and waits
for SQL readiness. Doris runtime behavior is unchanged.
- Does this need documentation?
- [x] Yes: updated the fixture README and regression configuration
comments in this PR.
--
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
