MySQL to Redshift

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

Target DataSource：

Redshift

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.
Subscription Modification	Add, delete, or modify the subscribed tables with support for historical data migration. For more information, see Modify Subscription.
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.

Function	Description
Zero-Value Time Handling	Allow setting zero value for time to different data types to prevent errors when writing to the target.
Custom Code	For more information, see Custom Code Processing, Debug Custom Code and Logging in Custom Code.
Adding Virtual Columns	Support adding custom virtual columns with fixed values, such as region, ID, etc.
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.

Limit	Description
MySQL Storage Engine	Support InnoDB, MyISAM, AWS XEngine. Other storage engines have not been tested yet.
MySQL Character Set	Support utf8, utf8mb4, latin1. Other encodings have not been tested yet.
Primary Key Conflict Handling	PostgreSQL <= 9.4 or Greenplum <= 6 does not support conflict skipping or replacement. Performance may be affected when there are a large number of primary key conflicts.

Prerequisite	Description
Permissions for Account	See Permissions Required for MySQL/MariaDB.
Enabling Binlog	[mysqld] log-bin=mysql-bin # Enable Binlog binlog-format=ROW # Choose ROW mode binlog_row_image=FULL # Changes include all column data

Parameter	Description
parseBinlogParallel	Number of threads for parallel parsing of Binlog in Incremental DataJobs.
parseBinlogBufferSize	Size of the circular buffer for parsing Binlog in Incremental DataJobs.
maxTransactionSize	Maximum number of data rows per transaction. If exceeded, the transaction will be split and flushed in parts.
limitThroughputMb	Limit the throughput of incremental Binlogs.
extraDDL	Support synchronization of additional DDL, including PT, GHOST, ALI_DMS, and PT_GHOST.
needJsonEscape	Escape special characters in JSON to be written to the target database.
fullDataSqlConditionEnabled	Add filtering conditions in SQL during source data scanning. It only works in Full Data migration.
srcTimeZone	Source time zone, e.g., +08:00, Asia/Shanghai, America/New_York, etc.

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

Prerequisite	Description
Permissions for Account	Must have common SELECT, INSERT, DELETE, UPDATE, and DDL permissions.
Network Preparation	The sidecar node must be able to connect to the standard interactive interface of Redshift (e.g., 5439).

Parameter	Description
keyConflictStrategy	Strategy for handling primary key conflicts during incremental writes: IGNORE: Ignore conflicts (default) REPLACE: Replace on conflicts (optional)
dstWholeReplace	Convert INSERT and UPDATE operations into full-row replacement on the target.
enableTimeZoneProcess	Whether to enable time zone conversion for time fields.
timezone	Target time zone, e.g., +08:00, Asia/Shanghai, America/New_York.
defaultZeroDate	Default value for replacing '0000-00-00 00:00:00' / '0000-00-00' values. Optional values include: null (empty) Time (14:23:33) Date (1970-01-01) DateTime (1970-01-01 00:00:00), TimeZone Time (14:23:33+08:00 or 1970-01-01 00:00:00+08:00)
caseSensitive	Case sensitivity strategy for table names in SQL statements, including: UpperCase (Convert to uppercase) LowerCase (Convert to lowercase) Sensitive (Add qualifiers) NoSpecified (No conversion/No qualifiers)
writeStrategy	Target write strategy, including: ROW (Single row) MULTI_SQL (Multi-statement SQL) BATCH (Batch write, default option) COPY (PostgreSQL COPY command)
defaultGisSRID	Set the SRID for GIS data types.

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