Skip to main content

MariaDB

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

Setup

  1. Ensure your MariaDB instance is reachable from your data platform (network routing, firewall rules, and allowlists as needed).
  2. Create (or choose) a target database and schema where tables will be created/updated.
  3. Create a database user for the connector with permissions to create and write to tables in the target schema.

Authentication

Configure the connector with MariaDB connection credentials:

  • Host and Port for your MariaDB server
  • Username and Password
  • Database (the default database to connect to)

If your environment requires TLS/SSL, configure your MariaDB server accordingly and provide the required connection settings in your platform’s MariaDB destination configuration.

Configuration

Provide the following fields when creating the destination:

FieldTypeRequiredDescription
hoststringMariaDB server hostname or IP address.
portnumberMariaDB server port (commonly 3306).
userstringUsername used to connect to MariaDB.
passwordstringPassword for the MariaDB user.
databasestringDefault database to connect to and load into.
schemastringTarget schema/database namespace to load into (if applicable in your environment).

Loading behavior

  • The connector loads records into tables in the configured database (and schema, if provided).
  • Tables and columns may be created or altered as needed to match incoming data, depending on your platform’s standard destination behavior for SQL databases.

Streams

This is a destination connector. It does not expose source streams. Instead, it receives one or more modeled datasets from your pipeline and writes them as tables in MariaDB.

Data types

MariaDB is MySQL-compatible, and the connector maps incoming types to appropriate MariaDB column types where possible. Exact type mapping can vary based on the incoming schema and the destination’s SQL type support.

If you encounter a type mismatch, consider adjusting the upstream model to cast fields into compatible SQL types.

Troubleshooting

  • Login fails: Verify host/port reachability, credentials, and that the MariaDB user is allowed to connect from the connector’s network location.
  • Permission errors: Ensure the user has privileges to create/alter tables and insert/update rows in the target database/schema.
  • Connectivity issues: Check firewall rules, VPC/security group settings, and any required TLS settings.