voonhous opened a new issue, #19059: URL: https://github.com/apache/hudi/issues/19059
`hudi-integ-test`'s test-suite query nodes are pinned to stale JDBC clients: - `trino.version=390` -- `io.trino:trino-jdbc`, used by `TrinoQueryNode` - `presto.version=0.273` -- `com.facebook.presto:presto-jdbc`, used by `PrestoQueryNode` Both lag well behind current releases. After the RFC-105 connector migration (#18837), the connector compiles against Trino SPI **481** (`trino.connector.version`), so the integ-test `trino.version` (390) is now out of step with the connector. Bumping `TrinoQueryNode` to a current Trino would let us collapse `trino.version` into `trino.connector.version` and remove the split; `PrestoQueryNode`'s `presto-jdbc` should be refreshed in the same pass. ### Scope - Bump `trino-jdbc` (`TrinoQueryNode`) to a current Trino release; converge `trino.version` with `trino.connector.version`. - Bump `presto-jdbc` (`PrestoQueryNode`) to a current Presto release. - Verify the integ-test DAG query nodes still compile and run against the bumped clients. -- 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]
