Skip to main content

TDengine

Target DataSource：
MySQL

Connection

Basic Functions

FunctionDescription
Schema Migration

If the target schema does not exist, BladePipe will automatically generate and execute CREATE statements based on the source metadata and the mapping rule.

Full Data Migration

Migrate data by sequentially scanning data in tables and writing it in batches to the target database.

Incremental Data Sync

Sync of common DML like INSERT, UPDATE, DELETE is supported.
UPDATE and DELETE for tables without primary keys are not synced by default (manual selection required).

Data Verification and Correction

Verify all existing data. Optionally, you can correct the inconsistent data based on verification results. Scheduled DataTasks are supported.
For more information, see Create Verification and Correction DataJob.

Subscription Modification

Add, delete, or modify the subscribed tables with support for historical data migration. For more information, see Modify Subscription.

Position Resetting

Reset positions by offsets. Allow re-consumption of incremental data logs in a past period or since a specific offset.

Table Name Mapping

Support the mapping rules, namely, keeping the name the same as that in Source, converting the text to lowercase, converting the text to uppercase, truncating the name by "_digit" suffix.

Metadata Retrieval

Retrieve the target metadata with filtering conditions or target primary keys set from the source table.

Advanced Functions

FunctionDescription
Removal of Target Data before Full Data Migration

Remove the existing data in the Target before running the Full Data Migration, applicable for DataJobs reruning and scheduled Full Data migrations.

Recreating Target Table

Recreate target tables before running the Full Data Migration, applicable for DataJobs reruning and scheduled Full Data migrations.

Incremental Data Write Conflict Resolution Rule

IGNORE: Ignore primary key conflicts (skip writing), REPLACE: Replace the entire row in case of primary key conflicts.

Handling of Zero Value for Time

Allow setting zero value for time to different data types to prevent errors when writing to the Target.

Whole Database Sync

Support sync of DDLs to create, delete, and modify tables as well as the data. For more information, see Sync Whole Database.

Custom Code

For more information, see Custom Code Processing, Debug Custom Code and Logging in Custom Code.

Setting Target Primary Key

Change the primary key to another field to facilitate data aggregation and other operations.

Data Filtering Conditions

Support data filtering using WHERE conditions, with SQL-92 as the SQL language. For more information, see Data Filtering.

Subtable Subscription Filtering Conditions

For supertable sync, BladePipe supports subtable subscription filtering by WHERE condition. All subtables are subscribed by default. For more information, see TDengine Query Topic.

Examples

TitleDetails
Sync Data from TDengine to MySQL

See Sync Data from TDengine to MySQL

Source

Prerequisites

PrerequisiteDescription
Permissions for Account

See Permissions Required for TDengine

Port Preparation

Allow the migration and sync node (Worker) to connect to the TDengine Websocket port (e.g., 6041).

Parameters

ParameterDescription
fullBatchSize

The number of records written in a single batch to the target instance. It has a significant impact on migration performance.

fullPagingCount

The page size for scanning a source relational database.

consumeParallel

The number of concurrent consumption in source instance. It is recommended to be consistent with the number of vnode.

supportTimestampToEpochNano

Whether to convert timestamps to nanosecond-level integers.

Tips: To modify the general parameters, see General Parameters and Functions.

Target

Prerequisites

PrerequisiteDescription
Permissions for Account

See Permissions Required for MySQL/MariaDB.

Port Preparation

Allow the migration and sync node (Worker) to connect to the MySQL/MariaDB port (e.g., 3306).

Parameters

ParameterDescription
keyConflictStrategy

Strategy for handling primary key conflicts during write in Incremental DataTask:

  • IGNORE: Ignore conflicts (default)
  • REPLACE: Replace conflicts (optional)

dstWholeReplace

Convert INSERT and UPDATE operations into full row replacement in the Target.

deCycle

Enable filtering in bidirectional sync to filter DML/DDL with specific markers.

specialSqlMode

Set a specific SQL mode when initializing the connection between databases.

defaultGisSRID

Set the SRID for GIS data types.

dstTimeZone

Target time zone, e.g., +08:00, Asia/Shanghai, America/New_York, etc.

increParallelApplyStrategy

Parallel write strategy for relational databases in the Target:

  • KEY: Parallel writing to partitions separated based on primary keys.
  • TABLE: Parallel writing to partitions separated based on tables.
  • KEY_UPGRADE_TABLE: Parallel writing to partitions separated based on primary keys. Upgrade the partition to a table if there is an update to the unique key.

Tips: To modify the general parameters, see General Parameters and Functions.

Connection​

Basic Functions​

Advanced Functions​

Limits​

Example​

FAQ​

Source​

Prerequisites​

Parameters​

Target​

Prerequisites​

Parameters​