Build PostgreSQL-Connected ETL Processes in Google Data Fusion

Google Data Fusion allows users to perform self-service data integration to consolidate disparate data. Uploading the CData JDBC Driver for PostgreSQL enables users to access live PostgreSQL data from within their Google Data Fusion pipelines. While the CData JDBC Driver enables piping PostgreSQL data to any data source natively supported in Google Data Fusion, this article explains how to pipe data from PostgreSQL to Google BigQuery,

Upload the CData JDBC Driver for PostgreSQL to Google Data Fusion

Upload the CData JDBC Driver for PostgreSQL to your Google Data Fusion instance to work with live PostgreSQL data. Due to the naming restrictions for JDBC drivers in Google Data Fusion, create a copy or rename the JAR file to match the following format driver-version.jar. For example: cdatapostgresql-2020.jar

1. Open your Google Data Fusion instance
2. Click the to add an entity and upload a driver 👁 Image
   
3. On the "Upload driver" tab, drag or browse to the renamed JAR file.
4. On the "Driver configuration" tab:
   • Name: Create a name for the driver (cdata.jdbc.postgresql) and make note of the name
   • Class name: Set the JDBC class name: (cdata.jdbc.postgresql.PostgreSQLDriver)
   👁 Configuring the driver (Salesforce is shown.)
   
5. Click "Finish"

Connect to PostgreSQL Data in Google Data Fusion

With the JDBC Driver uploaded, you are ready to work with live PostgreSQL data in Google Data Fusion Pipelines.

1. Navigate to the Pipeline Studio to create a new Pipeline
2. From the "Source" options, click "Database" to add a source for the JDBC Driver 👁 Adding a database source
   
3. Click "Properties" on the Database source to edit the properties

   NOTE: To use the JDBC Driver in Google Data Fusion, you will need a license (full or trial) and a Runtime Key (RTK). For more information on obtaining this license (or a trial), contact our sales team.

   • Set the Label
   • Set Reference Name to a value for any future references (i.e.: cdata-postgresql)
   • Set Plugin Type to "jdbc"
   • Set Connection String to the JDBC URL for PostgreSQL. For example:
     
     jdbc:postgresql:RTK=5246...;User=postgres;Password=admin;Database=postgres;Server=127.0.0.1;Port=5432;

     To connect to PostgreSQL, set the Server, Port (the default port is 5432), and Database connection properties and set the User and Password you wish to use to authenticate to the server. If the Database property is not specified, the data provider connects to the user's default database.

     SSH Connectivity for PostgreSQL

     You can use SSH (Secure Shell) to authenticate with PostgreSQL, whether the instance is hosted on-premises or in supported cloud environments. SSH authentication ensures that access is encrypted (as compared to direct network connections).

     SSH Connections to PostgreSQL in Password Auth Mode

     To connect to PostgreSQL via SSH in Password Auth mode, set the following connection properties:

     • User: PostgreSQL User name
     • Password: PostgreSQL Password
     • Database: PostgreSQL database name
     • Server: PostgreSQL Server name
     • Port: PostgreSQL port number like 3306
     • UserSSH: "true"
     • SSHAuthMode: "Password"
     • SSHPort: SSH Port number
     • SSHServer: SSH Server name
     • SSHUser: SSH User name
     • SSHPassword: SSH Password

     SSH Connections to PostgreSQL in Public Key Auth Mode

     To connect to PostgreSQL via SSH in Password Auth mode, set the following connection properties:

     • User: PostgreSQL User name
     • Password: PostgreSQL Password
     • Database: PostgreSQL database name
     • Server: PostgreSQL Server name
     • Port: PostgreSQL port number like 3306
     • UserSSH: "true"
     • SSHAuthMode: "Public_Key"
     • SSHPort: SSH Port number
     • SSHServer: SSH Server name
     • SSHUser: SSH User name
     • SSHClientCret: the path for the public key certificate file

     Built-in Connection String Designer

     For assistance in constructing the JDBC URL, use the connection string designer built into the PostgreSQL JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.

      java -jar cdata.jdbc.postgresql.jar
      

     Fill in the connection properties and copy the connection string to the clipboard.

     👁 Using the built-in connection string designer to generate a JDBC URL (Salesforce is shown.)
     
   • Set Import Query to a SQL query that will extract the data you want from PostgreSQL, i.e.:
     SELECT * FROM Orders
   👁 Configuring the database source
   
4. From the "Sink" tab, click to add a destination sink (we use Google BigQuery in this example)
5. Click "Properties" on the BigQuery sink to edit the properties
   • Set the Label
   • Set Reference Name to a value like postgresql-bigquery
   • Set Project ID to a specific Google BigQuery Project ID (or leave as the default, "auto-detect")
   • Set Dataset to a specific Google BigQuery dataset
   • Set Table to the name of the table you wish to insert PostgreSQL data into
   👁 Configuring the BigQuery sink
   

With the Source and Sink configured, you are ready to pipe PostgreSQL data into Google BigQuery. Save and deploy the pipeline. When you run the pipeline, Google Data Fusion will request live data from PostgreSQL and import it into Google BigQuery. 👁 Image

While this is a simple pipeline, you can create more complex PostgreSQL pipelines with transforms, analytics, conditions, and more. Download a free, 30-day trial of the CData JDBC Driver for PostgreSQL and start working with your live PostgreSQL data in Google Data Fusion today.