ewangsdc commented on PR #3: URL: https://github.com/apache/flink-connector-jdbc/pull/3#issuecomment-1564695132
If the new Flink JDBC connector Trino dialect supports this Trino JDBC driver, i.e., https://trino.io/docs/current/client/jdbc.html & https://github.com/trinodb/docs.trino.io, Kerberos auth options could be added as extra options in addition to the current ones, i.e., https://nightlies.apache.org/flink/flink-docs-master/docs/connectors/table/jdbc/#connector-options:~:text=.id%3B-,Connector%20Options,-%23. Like Spark/PySpark session JDBC options for Trino Kerberos auth, the extra Flink JDBC connection options should include the Kerberos parameters s for the above Trino JDBC driver, e.g., 'kerberos_remote_service_name': "<service_name>", 'kerbeors_principal': "<principal>", 'kerberos_usecanonicalhostname': <True|False>, 'driver': 'io.trino.jdbc.TrinoDriver' Another option is to embed the above Kerberos parameters into the existing connection option url, i.e., JDBC database url, as one string, e.g, “jdbc:trino://<trino url>/<database>&KerberosRemoteServiceName=<service_name>&KerberosUseCanonicalHostname=False&......", and then Flink Trino dialect Java code should parse this url to get the Kerberos parameters and pass them to the above Trino JDBC driver . Thanks, Emerson -- 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]
