Skip to main content

TiDB

Overview​

The TiDB destination connector loads data into a TiDB database. TiDB is MySQL-compatible, and this connector uses a MySQL-compatible loading implementation under the hood.

Prerequisites​

  • A reachable TiDB cluster (host/port accessible from your data plane).
  • A TiDB user with permissions to create and write to tables in the target schema/database.
  • (Recommended) A dedicated database/schema for the destination workload.

Authentication​

Configure the connector using database credentials:

  • Username and password for a TiDB user
  • Host and port for the TiDB SQL endpoint
  • Database (schema) to write into

If your TiDB deployment requires TLS, configure your connection accordingly (for example, by using a TLS-enabled endpoint and providing the required certificates/parameters if your deployment mandates them).

Configuration​

Provide the following connection details when setting up the destination:

FieldTypeRequiredDescription
Hoststring✓TiDB host name or IP address.
Portnumber✓TiDB SQL port (commonly 4000).
Databasestring✓Target database/schema to load data into.
Usernamestring✓TiDB username.
Passwordstring✓TiDB password.

Data loading behavior​

  • The connector writes records into tables in the configured Database.
  • Table creation and write semantics follow MySQL-compatible behavior.

Hashing and normalization​

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

Data contract​

The TiDB destination loads tabular records into TiDB tables. The exact table and column mapping is determined by your destination configuration and the model/stream definitions in your workspace.

Streams​

This is a destination connector (Reverse ETL). It does not expose source streams.