Table of Contents

Search

  1. Preface
  2. Part 1: Introduction to Amazon Redshift connectors
  3. Part 2: Data Integration with Amazon Redshift V2 Connector
  4. Part 3: Data Integration with Amazon Redshift Connector

Amazon Redshift Connectors

Amazon Redshift Connectors

Advanced properties retained after the switch

Advanced properties retained after the switch

When you replace the source or target connection type in existing mappings or mapping tasks that use the Amazon Redshift V1 connection or the Amazon Redshift ODBC connection with the Amazon S3 V2 connection, you have the option to retain the configured advanced properties.
The following table lists the configured advanced source, lookup, and target properties from Amazon Redshift ODBC that are retained in Amazon Redshift V2 mappings:
Properties
Amazon Redshift ODBC properties retained in Amazon Redshift V2
Source
  • Pre SQL
  • Post SQL
  • SQL Override
Target
  • Pre SQL
  • Post SQL
The following table lists the configured advanced source, lookup, and target properties from Amazon Redshift V1 that are retained in Amazon Redshift V2 mappings:
Properties
Amazon Redshift V1 properties retained in Amazon Redshift V2
Source and Lookup
  • S3 Bucket Name
  • Enable Compression
  • Staging Directory Location
  • Unload Options
  • Encryption Type
  • Download S3 Files In Multiple Parts
  • 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
  • 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