PostgreSQL to Kudu

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

Target DataSource：

Kudu

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.
Metadata Retrieval	Retrieve the target metadata with filtering conditions or target primary keys set from the source table.

Function	Description
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.

Prerequisite	Description
Permissions for Account	Required permissions (taking a self-managed database as an example): GRANT ALL PRIVILEGES ON DATABASE sync_db TO sync_user (or SELECT permission on all views in the sync_db information_schema, and SELECT permission on tables, indexes, constraints to be synchronized) ALTER USER sync_user REPLICATION
Incremental Data Sync Preparation	Prepare as follows: Modify postgresql.conf, set wal_level=logical and wal_log_hints=on Modify pg_hba.conf, set host replication sync_user CIDR netmask md5, host sync_db sync_user CIDR netmask md5, host postgres sync_user CIDR netmask md5 Restart PostgreSQL
Port Preparation	Allow the migration and sync node (Worker) to connect to the PostgreSQL port (e.g., port 5432).

Prerequisite

Description

Permissions for Account

Required permissions (taking a self-managed database as an example):

GRANT ALL PRIVILEGES ON DATABASE sync_db TO sync_user (or SELECT permission on all views in the sync_db information_schema, and SELECT permission on tables, indexes, constraints to be synchronized)
ALTER USER sync_user REPLICATION

Incremental Data Sync Preparation

Prepare as follows:

Modify postgresql.conf, set wal_level=logical and wal_log_hints=on
Modify pg_hba.conf, set host replication sync_user CIDR netmask md5, host sync_db sync_user CIDR netmask md5, host postgres sync_user CIDR netmask md5
Restart PostgreSQL

Port Preparation

Allow the migration and sync node (Worker) to connect to the PostgreSQL port (e.g., port 5432).

Parameter	Description
fullFetchSize	Fetch size for scaning full data.
eventStoreSize	Cache size for parsed incremental events.
ignoreGisSRID	Whether to ignore SRID when parsing GIS data types.
defaultGisSRID	Set the SRID for GIS data types.

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

Prerequisite	Description
Network Preparation	The sidecar node must be able to connect to Kudu Masters and Tablet Server nodes.

Parameter	Description
writeParallel	Number of parallel writes to the target.
batchSize	Maximum number of records per single write.
retryCount	Number of retries on write errors.

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