TiDB to StarRocks

BladePipe supports data replication from TiDB to StarRocks. View supported migration, sync, verification, and connector capabilities.

Target DataSource：

StarRocks

Connection

Function	Description
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.
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 timestamp to consume again the incremental data that has not been collected as garbage by TiKV in a past period.
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.
DDL Sync	ALTER TABLE ADD COLUMN, MODIFY COLUMN, DROP COLUMN CREATE TABLE RENAME TABLE DROP TABLE
Metadata Retrieval	Retrieve the target metadata with filtering conditions or target primary keys set from the source table.

Function	Description
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.
Stream Load	Use Stream Load to write data to StarRocks BE. By default, batch write is adopted, with dynamic adjustment of data flush interval and batch size.
Handling of Zero Value for Time	Allow setting zero value for time to different data types to prevent errors when writing to the Target.
Custom Table Properties	Include settings for properties such as bucket count and replica count.
Setting Data Partitions	When creating a DataJob, specify partition definitions at the table level (static or dynamic). Automatically add these partition definitions during schema migration.
Scheduled Full Data Migration	For more information, see Create Scheduled Full Data DataJob.
Custom Code	For more information, see Custom Code Processing, Debug Custom Code and Logging in Custom Code.
Data Filtering Conditions	Support data filtering using WHERE conditions, with SQL-92 as the SQL language. For more information, see Data Filtering.

Limit	Description
Target Table Type	Only support Primary Key model.
Source Table Type	Migration and sync of tables without primary keys are not supported.
DDL Synchronization Errors	Continuous DDLs on the same table will cause errors (because asynchronous DDLs are executed on a target StarRocks instance). Errors may occur when modifying field constraints or some types of DDL. If DDL errors occur, you can change the target table schema and then skip the errors by setting DataJob parameters.
Incremental Data Write Conflict Resolution Rule	Using Stream Load method, the primary key is used for full row replacement.

Prerequisite	Description
Permissions for Account	See Permissions Required for TiDB.
Connection to PD Nodes	Make sure that BladePipe Workers can communicate with PD nodes. telnet [PD Node IP] [PD Node Port]
TiKV GC Frequency	Set GC cycle to 24 hours or more in TiDB Server. set global tidb_gc_life_time = "24h0m0s";
TiKV Historical Data Caching	Adjust the size based on task needs. old-value-cache-memory-quota: Upper limit of memory used by past incremental data on TiKV nodes sink-memory-quota: Upper limit of memory used by incremental data on TiKV nodes

Parameter	Description
printDetailLog	Print received incremental data. It is used for determining if the source database has incremental data.
pdHost	PD node address for DataJob requests. Format: [PD_IP]:[PD_PORT], multiple PD nodes separated by , Example: 127.0.0.1:2379,127.0.0.1:2380
cdcGrpcTimeout	Timeout for gRPC channel of PD nodes to DataJob, in ms.
cdcStubTimeout	Timeout for each stub in gRPC channel, in ms. Auto-resubscribe the stub in case of time out.
fastFailKeywords	A comma-separated array of strings. When an exception message contains any of these keywords, the task will skip reconnection attempts and restart directly. For example, DEADLINE_EXCEEDED means the task will restart directly instead of reconnecting when a gRPC timeout exception occurs.

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

Prerequisite	Description
Permissions for Account	SELECT and DDL permissions (optional)
Port Preparation	Allow the migration and sync node (Worker) to connect to the StarRocks FE QueryPort and FE/BE HttpPort.

Parameter	Description
host	MySQL port, corresponding to StarRocks FE QueryPort.
httpHost	Host for StarRocks stream load, corresponding to StarRocks FE/BE HttpPort.
totalDataInMemMb	Maximum data size allowed in memory when writing in batches; If the data size exceeds the memory limit, or the wait time exceeds asyncFlushIntervalSec, then data is flushed to the write queue.
asyncFlushIntervalSec	Interval to wait for flushing when writing in batches; If the wait time exceeds asyncFlushIntervalSec, or the data size exceeds totalDataInMemMb, then data is flushed to the write queue.
flushBatchMb	Maximum batch size per table; If the batch size exceeds this limit, then data is flushed to the write queue.
realFlushPauseSec	Wait time to flush data to StarRocks using stream load, 0 means no wait is needed.
soTimeoutSec	TCP socket timeout (so_timeout) during QueryPort operations.
httpSoTimeoutSec	TCP socket timeout (so_timeout) during HttpPort operations.
enableTimeZoneProcess	Enable time zone conversion for time fields.
timezone	Timezone in the Target, e.g., +08:00 Asia/Shanghai America/New_York.
maxInSizePerQuery	Maximum number of IN clause values per query during secondary verification. Queries exceeding this limit will be automatically split.

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