Aurora for PostgreSQL to Iceberg

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

Target DataSource：

Iceberg

Connection

Basic Functions

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.
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 file position or timestamp. Allow re-consumption of incremental data logs in a past period or since a specific Binlog file and position.
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, DROP COLUMN, MODIFY COLUMN, CHANGE COLUMN
Metadata Retrieval	Retrieve the target metadata with filtering conditions or target primary keys set from the source table.

Advanced Functions

Function	Description
Write Conflict Resolution Rule	For the source tables with primary keys, data is overwritten to the Target. For the source tables without primary keys, data is appended to the Target.
Custom Table Properties	Configure format-version and other table properties.
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.
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.

---

Source

Prerequisites

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).

Parameters

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.

---

Target

Prerequisites

Prerequisite	Description
Port Preparation	Allow the migration and sync node (Worker) to connect to the catalogs and FileIO.
Nessie Catalog Configuration Template	CatalogUri: ip:19120/api/v1 catalogName: nessie catalogType: NESSIE catalogWarehouse: s3://warehouse catalogProps: { "io-impl": "org.apache.iceberg.aws.s3.S3FileIO", "s3.endpoint": "http://ip:9000", "s3.access-key-id": "admin", "s3.secret-access-key": "password", "s3.path-style-access": "true", "client.region": "ap-southeast-1" }
Glue Data Catalog Configuration Template	CatalogUri: glue.ap-southeast-1.amazonaws.com httpsEnabled: true catalogName: glue_catalog catalogType: GLUE catalogWarehouse : s3://warehouse catalogProps: { "io-impl": "org.apache.iceberg.aws.s3.S3FileIO", "s3.endpoint": "https://s3.ap-southeast-1.amazonaws.com", "s3.access-key-id": "", "s3.secret-access-key": "", "s3.path-style-access": "true", "client.region": "ap-southeast-1", "client.credentials-provider.glue.access-key-id": "", "client.credentials-provider.glue.secret-access-key": "", "client.credentials-provider": "com.amazonaws.glue.catalog.credentials.GlueAwsCredentialsProvider" }
REST Catalog Configuration Template	CatalogUri: ip :8181 httpsEnabled: false catalogName: rest_catalog catalogType: REST catalogWarehouse : s3://warehouse catalogProps: { "io-impl": "org.apache.iceberg.aws.s3.S3FileIO", "s3.endpoint": "http://ip:9000", "s3.access-key-id": "admin", "s3.secret-access-key": "password", "s3.path-style-access": "true", "client.region": "us-east-1" }

Parameters

Parameter	Description
fileFormat	Format of the file to write data to (parquet/orc/...)
writeTargetFileSizeMb	Size of the target file to write data to (MB).
writeProps	Data Write Parameters to configure (Json format).
commitBranch	Branch to commit.
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 Iceberg using Bulk Write. 0 means no wait is needed.

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