Build SingleStore-Connected ETL Processes in Google Data Fusion

Ready to get started?

Download for a free trial:

Download Now

Learn more:

SingleStore JDBC Driver

Rapidly create and deploy powerful Java applications that integrate with SingleStore.



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

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

Upload the CData JDBC Driver for SingleStore to Google Data Fusion

Upload the CData JDBC Driver for SingleStore to your Google Data Fusion instance to work with live SingleStore 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: cdatasinglestore-2020.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.singlestore) and make note of the name
    • Class name: Set the JDBC class name: (cdata.jdbc.singlestore.SingleStoreDriver)
  5. Click "Finish"

Connect to SingleStore Data in Google Data Fusion

With the JDBC Driver uploaded, you are ready to work with live SingleStore 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

    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-singlestore)
    • Set Plugin Type to "jdbc"
    • Set Connection String to the JDBC URL for SingleStore. For example:

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

      The following connection properties are required in order to connect to data.

      • Server: The host name or IP of the server hosting the SingleStore database.
      • Port: The port of the server hosting the SingleStore database.
      • Database (Optional): The default database to connect to when connecting to the SingleStore Server. If this is not set, tables from all databases will be returned.

      Connect Using Standard Authentication

      To authenticate using standard authentication, set the following:

      • User: The user which will be used to authenticate with the SingleStore server.
      • Password: The password which will be used to authenticate with the SingleStore server.

      Connect Using Integrated Security

      As an alternative to providing the standard username and password, you can set IntegratedSecurity to True to authenticate trusted users to the server via Windows Authentication.

      Connect Using SSL Authentication

      You can leverage SSL authentication to connect to SingleStore data via a secure session. Configure the following connection properties to connect to data:

      • SSLClientCert: Set this to the name of the certificate store for the client certificate. Used in the case of 2-way SSL, where truststore and keystore are kept on both the client and server machines.
      • SSLClientCertPassword: If a client certificate store is password-protected, set this value to the store's password.
      • SSLClientCertSubject: The subject of the TLS/SSL client certificate. Used to locate the certificate in the store.
      • SSLClientCertType: The certificate type of the client store.
      • SSLServerCert: The certificate to be accepted from the server.

      Connect Using SSH Authentication

      Using SSH, you can securely login to a remote machine. To access SingleStore data via SSH, configure the following connection properties:

      • SSHClientCert: Set this to the name of the certificate store for the client certificate.
      • SSHClientCertPassword: If a client certificate store is password-protected, set this value to the store's password.
      • SSHClientCertSubject: The subject of the TLS/SSL client certificate. Used to locate the certificate in the store.
      • SSHClientCertType: The certificate type of the client store.
      • SSHPassword: The password that you use to authenticate with the SSH server.
      • SSHPort: The port used for SSH operations.
      • SSHServer: The SSH authentication server you are trying to authenticate against.
      • SSHServerFingerPrint: The SSH Server fingerprint used for verification of the host you are connecting to.
      • SSHUser: Set this to the username that you use to authenticate with the SSH server.

      Built-in Connection String Designer

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

      java -jar cdata.jdbc.singlestore.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 SingleStore, 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 singlestore-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 SingleStore data into

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

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