Ready to get started?

Download a free trial of the SingleStore Driver to get started:

 Download Now

Learn more:

SingleStore Icon SingleStore JDBC Driver

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

Integrate SingleStore with External Services using SnapLogic



Use the CData JDBC Driver for SingleStore in SnapLogic to integrate SingleStore with External Services.

SnapLogic is an integration platform-as-a-service (iPaaS) that allows users to create data integration flows with no code. When paired with the CData JDBC Drivers, users get access to live data from more than 250+ SaaS, Big Data and NoSQL sources, including SingleStore, in their SnapLogic workflows.

With built-in optimized data processing, the CData JDBC Driver offers unmatched performance for interacting with live SingleStore data. When platforms issue complex SQL queries to SingleStore, the driver pushes supported SQL operations, like filters and aggregations, directly to SingleStore and utilizes the embedded SQL engine to process unsupported operations client-side (often SQL functions and JOIN operations). Its built-in dynamic metadata querying lets you work with SingleStore data using native data types.

Connect to SingleStore in SnapLogic

To connect to SingleStore data in SnapLogic, download and install the CData SingleStore JDBC Driver. Follow the installation dialog. When the installation is complete, the JAR file can be found in the installation directory (C:/Program Files/CData/CData JDBC Driver for SingleStore/lib by default).

Upload the SingleStore JDBC Driver

After installation, upload the JDBC JAR file to a location in SnapLogic (for example, projects/Jerod Johnson) from the Manager tab.

Configure the Connection

Once the JDBC Driver is uploaded, we can create the connection to SingleStore.

  1. Navigate to the Designer tab
  2. Expand "JDBC" from Snaps and drag a "Generic JDBC - Select" snap onto the designer
  3. Click Add Account (or select an existing one) and click "Continue"
  4. In the next form, configure the JDBC connection properties:
    • Under JDBC JARs, add the JAR file we previously uploaded
    • Set JDBC Driver Class to cdata.jdbc.singlestore.SingleStoreDriver
    • Set JDBC URL to a JDBC connection string for the SingleStore JDBC Driver, for example:

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

      NOTE: RTK is a trial or full key. Contact our Support team for more information.

      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.

      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.
  5. After entering the connection properties, click "Validate" and "Apply"

Read SingleStore Data

In the form that opens after validating and applying the connection, configure your query.

  • Set Schema name to "SingleStore"
  • Set Table name to a table for SingleStore using the schema name, for example: "SingleStore"."Orders" (use the drop-down to see the full list of available tables)
  • Add Output fields for each item you wish to work with from the table

Save the Generic JDBC - Select snap.

With connection and query configured, click the end of the snap to preview the data (highlighted below).

Once you confirm the results are what you expect, you can add additional snaps to funnel your SingleStore data to another endpoint.

Piping SingleStore Data to External Services

For this article, we will load data in a Google Spreadsheet. You can use any of the supported snaps, or even use a Generic JDBC snap with another CData JDBC Driver, to move data into an external service.

  1. Start by dropping a "Worksheet Writer" snap onto the end of the "Generic JDBC - Select" snap.
  2. Add an account to connect to Google Sheets
  3. Configure the Worksheet Writer snap to write your SingleStore data to a Google Spreadsheet

You can now execute the fully configured pipeline to extract data from SingleStore and push it into a Google Spreadsheet.

Piping External Data to SingleStore

As mentioned above, you can also use the JDBC Driver for SingleStore in SnapLogic to write data to SingleStore. Start by adding a Generic JDBC - Insert or Generic JDBC - Update snap to the dashboard.

  1. Select the existing "Account" (connection) or create a new one
  2. Configure the query:
    • Set Schema name to "SingleStore"
    • Set Table name to a table for SingleStore using the schema name, for example: "SingleStore"."Orders" (use the drop-down to see the full list of available tables)
  3. Save the Generic JDBC - Insert/Update snap

At this point, you have configured a snap to write data to SingleStore, inserting new records or updating existing ones.

More Information & Free Trial

Using the CData JDBC Driver for SingleStore you can create a pipeline in SnapLogic for integrating SingleStore data with external services. For more information about connecting to SingleStore, check at our CData JDBC Driver for SingleStore page. Download a free, 30 day trial of the CData JDBC Driver for SingleStore and get started today.