Skip to main content

SingleStore

The SingleStore destination lets you load data into a SingleStore database. This connector uses a MySQL-compatible implementation, so it works with SingleStore deployments that accept standard MySQL connections.

Setup​

  1. Network access

    • Ensure the destination runner can reach your SingleStore host and port.
    • If your SingleStore deployment is behind a firewall/VPC, allowlist the runner’s egress IPs or set up the appropriate private networking.

  2. Database user permissions Create (or use) a database user with permissions to write to the target schema and tables. At minimum, the user should be able to:

    • Create tables (if your workflow creates them)
    • Insert/update rows in the target tables

  3. Collect connection details You’ll need:

    • Host
    • Port
    • Database name
    • Username and password
    • (Optional) TLS/SSL settings, if required by your deployment

Authentication​

SingleStore destination authentication is done using username + password over a MySQL-compatible connection.

Configuration fields​

Configure the destination with the following fields:

FieldTypeRequiredDescription
Hoststring✅The hostname or IP address of your SingleStore endpoint.
Portinteger✅The port for MySQL-compatible connections (commonly 3306, but may differ in your environment).
Databasestring✅The target database name.
Usernamestring✅The database user to connect as.
Passwordstring✅The password for the database user.

Hashing and normalization​

This destination connector does not currently expose field-level hashing controls in its public configuration.

Data contract​

This destination loads records into your configured SingleStore database using a MySQL-compatible writer. The exact table/column mapping and keying behavior depends on the Reverse ETL model and how your workspace is configured to materialize records (for example, which fields are used as identifiers and which are treated as attributes).

Streams​

As a Reverse ETL destination, SingleStore does not expose source streams. It receives the modeled records produced by your Reverse ETL and writes them into the configured database tables.