SingleStore
Overview
SingleStore is a distributed SQL database for high-throughput transactions, including inserts and upserts. It provides low-latency analytics and context from real-time vector data.
Features
| Feature | Supported | Notes |
|---|---|---|
| Full Refresh Sync | Yes | |
| Incremental - Append Sync | Yes | |
| Change Data Capture | No | |
| SSL Support | Yes | |
| SSH Tunnel Connection | Yes |
Below, you’ll find a ‘Quick Start’ guide, advanced setup steps and reference information, including data type mapping and changelogs.
Get started
Requirements
- A SingleStore instance
- Allow connections from Airbyte to your SingleStore database (if they’re in separate VPCs)
- Create a dedicated, read-only Airbyte user with access to every table needed for replication
1. Make your database accessible from the machine running Airbyte
The required steps depend on your network setup. Use the check connection tool in the UI to confirm Airbyte can connect to your SingleStore instance.
2. Create a dedicated, read-only user for the relevant tables (Recommended but optional)
This optional step gives you better permission control and auditing. Alternatively, you can connect Airbyte using an existing database user.
Create a dedicated database user by running these commands against your database:
CREATE
USER airbyte IDENTIFIED BY <your_password_here>;
Next, give the user read-only access to the relevant tables. The simplest approach grants read access to every table in the database:
GRANT
SELECT
ON <your_database_name_here>.* TO airbyte;
For more granular access, use:
GRANT SELECT ON "<database_a>"."<table_1>" TO airbyte;
GRANT SELECT ON "<database_b>"."<table_2>" TO airbyte;
Your database user is now ready to use with Airbyte.
Connect with SSL or SSH Tunneling
SSL modes
Choose from these SSL connection modes:
disabledisables encrypted communication between Airbyte and the sourcerequiredalways requires encryption. The connection fails if the source doesn’t support encryption.verify-caalways requires encryption and verifies that the source has a valid SSL certificateverify-fullalways requires encryption and verifies the source’s identity
Connect through an SSH Tunnel
Airbyte can connect to a SingleStore instance through an SSH Tunnel. Use this method when direct database access is unavailable or conflicts with your security policy. For example, the database might not have a public IP address.
With an SSH tunnel, Airbyte connects to an intermediate server, also called a bastion server. This server has direct database access. Airbyte connects to the bastion, which then connects directly to the database server.
This feature needs extra configuration when you create the source. The following steps explain each configuration setting.
- Configure every source field as usual, except
SSH Tunnel Method. SSH Tunnel Methoddefaults toNo Tunnel, which creates a direct connection. For an SSH Tunnel, chooseSSH Key AuthenticationorPassword Authentication.- Choose
Key Authenticationwhen using an RSA private key to establish the SSH Tunnel. See below for key-generation details. - Choose
Password Authenticationwhen using a password to establish the SSH Tunnel.
- Choose
SSH Tunnel Jump Server Hostidentifies the intermediate, or bastion, server that Airbyte connects to. Enter its hostname or IP Address.SSH Connection Portis the bastion server port used for the SSH connection. The default SSH port is22. Keep this default unless you’ve explicitly changed the port.SSH Login Usernameis the username Airbyte uses to connect to the bastion server. This is NOT the SingleStore username.- With
Password Authentication, setSSH Login Usernameto the previous step’s User password. WithSSH Key Authentication, leave this blank. This isn’t the SingleStore password. It’s the OS-user password Airbyte uses to run commands on the bastion. - With
SSH Key Authentication, setSSH Private Keyto the RSA Private Key used for the SSH connection. Include the key file’s full contents, starting with-----BEGIN RSA PRIVATE KEY-----and ending with-----END RSA PRIVATE KEY-----.
Generate a private key for SSH Tunneling
The connector requires an RSA key in PEM format. Generate the key as follows:
ssh-keygen -t rsa -m PEM -f myuser_rsa
This creates the private key in PEM format. The public key remains in the standard format used by your bastion host’s authorized_keys file. Add the public key to the bastion host for the user you’ll connect with through Airbyte. Copy and paste the private key into the Airbyte connector configuration screen. Airbyte can then use it to log in to the bastion.
Data type mapping
When you synchronise data, SingleStore data types map to the following data types.
| SingleStore Type | Resulting Type | Notes |
|---|---|---|
BIT | base64 binary string | |
TINYINT | number | |
SMALLINT | number | |
MEDIUMINT | number | |
INT | number | |
BIGINT | number | |
FLOAT | number | |
DOUBLE | number | |
DECIMAL | number | |
DATE | string | |
TIME | string | |
DATETIME | string | |
TIMESTAMP | string | |
YEAR | year string | |
CHAR | string | |
VARCHAR | string | |
LONGTEXT | string | |
MEDIUMTEXT | string | |
TEXT | string | |
TINYTEXT | string | |
BINARY | base64 binary string | |
VARBINARY | base64 binary string | |
LONGBLOB | base64 binary string | |
MEDIUMBLOB | base64 binary string | |
BLOB | base64 binary string | |
TINYBLOB | base64 binary string | |
JSON | serialized json string | |
ENUM | string | |
SET | string | |
GEOGRAPHYPOINT | string | |
GEOGRAPHY | string | |
VECTOR | string |
IP allow list
If you use Airbyte Cloud and restrict access to specific IPs, add the Airbyte Cloud IP addresses to your allow list.
Changelog
| Version | Date | Pull Request | Subject |
|---|---|---|---|
| 0.1.4 | 2025-07-10 | 62925 | Convert to new gradle build flow |
| 0.1.3 | 2025-05-08 | 59722 | Consolidate gradle setup. |
| 0.1.2 | 2025-01-10 | 51501 | Use a non root base image |
| 0.1.1 | 2024-12-18 | 49862 | Use a base image: airbyte/java-connector-base:1.0.0 |
| 0.1.0 | 2024-04-16 | 37337 | Add SingleStore source connector |