What happened?

I'm using the python beam WriteToJdbc transform with Google Cloud providing the cloud-sql-jdbc-socket-factory Postgres fat jar via the transforms classpath parameter that outline the format of the JDBC url as:

String jdbcUrl = "jdbc:postgresql:///<DATABASE_NAME>?" 
    + "cloudSqlInstance=<INSTANCE_CONNECTION_NAME>" 
    + "&socketFactory=com.google.cloud.sql.postgres.SocketFactory" 
    + "&user=<POSTGRESQL_USER_NAME>" 
    + "&password=<POSTGRESQL_USER_PASSWORD>";

This works as intended in my pipeline, however, I get unwanted INFO log statements from beam Java likely from here: "Failed to parse JdbcUrl {}. Lineage will not be reported.". The cloud-sql-jdbc-socket-factory documents indicate that part of the JDBC url is not used: "Note: The host portion of the JDBC URL is currently unused, and has no effect on the connection process. The SocketFactory will get your instances IP address based on the provided cloudSqlInstance arg.". Perhaps this is correct behavior to log this if cloud-sql-jdbc-socket-factory wants the JDBC URL to be that specific format when indeed this isn't a valid format (as INFO logged from beam Java). Any thoughts on this?

Issue Priority

Priority: 3 (minor)

Issue Components

• Component: Python SDK
• Component: Java SDK
• Component: Go SDK
• Component: Typescript SDK
• Component: IO connector
• Component: Beam YAML
• Component: Beam examples
• Component: Beam playground
• Component: Beam katas
• Component: Website
• Component: Infrastructure
• Component: Spark Runner
• Component: Flink Runner
• Component: Samza Runner
• Component: Twister2 Runner
• Component: Hazelcast Jet Runner
• Component: Google Cloud Dataflow Runner