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

Rules and guidelines for adding multiple source objects

Rules and guidelines for adding multiple source objects

Consider the following rules and guidelines when you add multiple source objects:
  • You cannot configure partitioning when you use the advanced relationship option.
  • You must specify double quotes for the table name when you use a reserved word for the table name and the column name.
  • You cannot use a self join when you add multiple source objects.
  • When you use special characters in column names for an advanced relationship, the query formed is not correct and the mapping task fails.
  • When you click
    Add Object
    to add more objects in the
    Advanced Relationship
    window, the table might not load or take a lot of time to load. Import the object again.
  • You cannot search for a schema when you add a related source object. You must scroll down and manually select the schema.
  • You can use the full outer-join condition only with the
    =
    ,
    ,
    , and
    AND
    operators.
  • When you use the advanced relationship option and specify the join queries with the schema name override, the mapping fails. The mapping fails with the following join queries:
    • inner join
    • left outer-join
    • right outer-join
    • full outer-join
    • cross join
  • When you override the schema name and configure an advanced filter on a related source object, you must specify the schema name in the filter condition. Use the following syntax for the filter condition:
    public.alldatatypes_src.f_smallint=1
  • When you override the schema name and configure an advanced filter on a related source object, the Secure Agent applies the advanced filter only on the parent object and not on the related source object.
  • When you select parent and child objects that have a primary key and foreign key relationship, and the foreign key of the related object is also a primary key in the table, the mapping task fails when you create a target.
  • When you select the
    Multiple Objects
    source type, add a source object, for example,
    emp
    , and define a primary key and foreign key relationship on different columns, for example,
    emp.id
    and
    dept.d_id
    , the mapping fails with the following error:
    [FATAL] Unload/Copy command failed with error: Invalid operation: column emp.d_id does not exist.
    The
    Select Related Objects
    list shows the join condition for the
    dept
    related object as
    emp.d_id=dept.d_id
    , even though the
    emp
    table does not have a
    d_id
    column.