diqiu50 opened a new issue, #12542: URL: https://github.com/apache/gravitino/issues/12542
### What would you like to be improved? The Trino connector registers catalogs by connecting back to the Trino coordinator over JDBC and running `CREATE CATALOG` / `DROP CATALOG`. `CatalogRegister.init()` sets only the `user` and `password` JDBC properties. As a result, the connection cannot be established against a coordinator that enables TLS or restricts `CREATE CATALOG` to a privileged role. None of the required driver properties is configurable, so the only workaround is to fork the connector and hardcode them. This affects every TLS-enabled and authorization-enabled Trino deployment. ### How should we improve? Add configuration properties for the internal JDBC connection: TLS enablement, truststore path, password and type, certificate verification mode, and session roles. Certificate verification should default to `FULL` rather than being disabled. Also add a passthrough prefix so that any other Trino JDBC driver property can be configured without patching the connector. These properties carry credentials and must not be propagated into the generated `CREATE CATALOG` statement, which is logged and persisted to the Trino catalog properties files. -- 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]
