Percona Server for MySQL
Introduction
The Percona Server for MySQL destination connector lets you load data into a Percona Server instance using MySQL-compatible connectivity and SQL semantics.
This destination is implemented as a MySQL-compatible destination, so configuration and behavior align with standard MySQL destinations.
Setup
- Ensure your Percona Server instance is reachable from the environment running the connector (network routing, firewall rules, and security groups).
- Create (or choose) a target database/schema to load into.
- Create a database user with permissions to create and write to the target tables.
Authentication
This connector authenticates using standard MySQL credentials:
- Host
- Port
- Username
- Password
- Database
If your Percona Server requires TLS, configure your instance and client connectivity accordingly (for example, by requiring SSL on the server side and providing the appropriate client settings in your deployment).
Configuration
Provide the following configuration fields when setting up the destination:
| Field | Type | Required | Description |
|---|---|---|---|
| Host | string | ✓ | Percona Server hostname or IP address. |
| Port | integer | ✓ | MySQL port (commonly 3306). |
| Username | string | ✓ | Database user for loading data. |
| Password | string | ✓ | Password for the database user. |
| Database | string | ✓ | Target database/schema to load data into. |
Hashing and normalization
This destination connector does not currently expose field-level hashing controls in its configuration.
Data contract
- Tables are created/updated in the configured Database.
- Column names and types are derived from the incoming records and the destination’s MySQL-compatible type mapping.
- Primary keys, upserts, and merge behavior (if applicable in your platform) follow the standard MySQL-compatible destination behavior.
Streams
This destination does not define its own source streams. It receives records from upstream models/streams in your pipeline and loads them into Percona Server tables according to your destination and sync configuration.