Ready to get started?

Learn more about the CData JDBC Driver for MariaDB or download a free trial:

Download Now

Build MariaDB-Connected ETL Processes in Google Data Fusion

Load the CData JDBC Driver into Google Data Fusion and create ETL processes with access live MariaDB data.

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

Upload the CData JDBC Driver for MariaDB to Google Data Fusion

Upload the CData JDBC Driver for MariaDB to your Google Data Fusion instance to work with live MariaDB 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 -.jar. For example: cdata.jdbc.mariadb-2019.jar

  1. Open your Google Data Fusion instance
  2. Click the to add an entity and upload a driver
  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.mariadb) and make note of the name
    • Class name: Set the JDBC class name: (cdata.jdbc.mariadb.MariaDBDriver)
  5. Click "Finish"

Connect to MariaDB Data in Google Data Fusion

With the JDBC Driver uploaded, you are ready to work with live MariaDB 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
  3. Click "Properties" on the Database source to edit the properties
    • Set the Label
    • Set Reference Name to a value for any future references (i.e.: cdata-mariadb)
    • Set Plugin Type to "jdbc"
    • Set Connection String to the JDBC URL for MariaDB. For example:

      jdbc:mariadb:RTK=5246...;User=myUser;Password=myPassword;Database=NorthWind;Server=myServer;Port=3306;

      The Server and Port properties must be set to a MariaDB server. If IntegratedSecurity is set to false, then User and Password must be set to valid user credentials. Optionally, Database can be set to connect to a specific database. If not set, the tables from all databases are reported.

      To use the JDBC Driver in Google Data Fusion, you will need to set the RTK property in the JDBC URL. You can view the licensing file included in the installation for information on how to set this property.

      Built-in Connection String Designer

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

      java -jar cdata.jdbc.mariadb.jar

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

    • Set Import Query to a SQL query that will extract the data you want from MariaDB, i.e.:
      SELECT * FROM Orders
  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 mariadb-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 MariaDB data into

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

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