Migrating a connector from previous versions using the Data Integration REST API

Migrating a connector from previous versions using the Data Integration REST API

Amazon Redshift

Amazon Redshift

The following table lists the configured advanced source, lookup, and target properties from Amazon Redshift V1 mappings that you can retain when you migrate to Amazon Redshift V2:
Transformations
Amazon Redshift V1 properties retained after migration to Amazon Redshift V2
Source and Lookup
  • S3 Bucket Name
  • Enable Compression
  • Staging Directory Location
  • Unload Options
  • Encryption Type
  • Download S3 Files In Multiple Parts
  • Source Table Name
  • Pre-SQL
  • Post-SQL
  • SQL-Query
  • Select Distinct
Target
  • S3 Bucket Name
  • Enable Compression
  • Staging Directory Location
  • S3 Client Side Encryption
  • S3 Server Side Encryption
  • Pre-SQL
  • Post-SQL
  • Batch Size
  • Number of Files per Batch
  • Max Errors Per Batch Upload Insert
  • Truncate Target Table Before Data Upload
  • Require Null Value For Char And Varchar
  • Wait Time In Seconds For S3 File Consistency
  • Copy Options
  • Vacuum Target Table
  • Analyze Target Table
  • Prefix to retain staging files on S3
  • Target Table Name
  • Minimum Upload Part Size
  • Success File Directory
  • Error File Directory
  • Transfer Manager Thread Pool Size

0 COMMENTS

We’d like to hear from you!