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

Amazon Redshift V2 objects in mappings

Amazon Redshift V2 objects in mappings

When you create a mapping, you can configure a Source or Target transformation to represent an Amazon Redshift V2 object.
Create a
mapping
task to process data based on the data flow logic defined in a mapping or integration template. You can also create a
mapping
task to capture changed data from the Oracle CDC source and write the changed data to an Amazon Redshift target table.
Rules and guidelines for Amazon Redshift V2 objects in mappings
Consider the following rules and guidelines when you configure Amazon Redshift V2 objects in mappings:
  • When you use a simple filter in a mapping, you must specify the filter condition in the
    YYYY-MM-DD HH24:MI:SS.MS
    format. If you use an advanced filter, you must specify the filter condition in the
    date_time_fix.f_timestamp < to_date('2012-05-24 09:13:57','YYYY-MM-DD HH24:MI:SS.MS')
    format.
  • When you define queries for sources or targets and the table names or the column names contain special characters, you must enclose the table names or column names in double quotes.
  • When you select an Amazon Redshift V2 object that contains a boolean data type and preview the data, the Secure Agent truncates the value of the boolean data type and displays only the first letter of the boolean value.
  • If a field contains a Date or Datetime data type, the
    Data Preview
    tab displays the field value with an offset of +4 hours.