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. Additionally, you can configure Lookups for mappings and mapping tasks.
Consider the following rules and guidelines when you configure Amazon Redshift V2 objects in mappings:
  • If 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.
  • To write special characters in the source column names to the target, you can configure a Target transformation in the mapping to create a new target at runtime. Enable the
    Exact Source Field Names in Target
    property in the
    Create New at Runtime
    window. You cannot view this checkbox if you select an existing object.
    This feature does not apply for mappings in advanced mode.
  • If the Amazon Redshift table or schema name contains a forward slash (/), the mapping fails.
  • When you select an Amazon Redshift V2 object that contains a boolean data type and preview the data, the value of the boolean data type appears truncated and displays only the first letter.
  • If a field contains a Date or Datetime data type, the
    Data Preview
    tab displays the field value with an offset of +4 hours.
  • When you read or write data using a mapping in advanced mode, the source table name must not contain unicode or special characters.

0 COMMENTS

We’d like to hear from you!