Cloud Data Integration Connectors All Products
When you push down a mapping with Amazon S3 as the source and Amazon Redshift as the target, the mapping runs successfully but the pushdown optimization fails.
The issue occurs when you use the
VARCHARdata type for the ORC source file or use the
Stringdata type for the JSON source file.
When you run a mapping that has an IAM role configured in COPY command options and the AWS Access key ID and AWS Secret Access Key connection properties are left blank, junk characters are displayed in the LOAD command in the session log.
When you read data from an Amazon S3 flat file with Shift JIS encoding, write to an Amazon Redshift target, and enable full pushdown optimization, the mapping fails.
When you parameterize an Amazon Redshift V2 source object and use advanced filter in the mapping task, the task fails due to an incorrect UNLOAD command.
When you enable full pushdown optimization for a mapping task, which contains a mapping that reads an Amazon S3 Avro source with column names in uppercase letters and uses an Amazon Redshift V2 connection to write data to an Amazon Redshift target, the COPY command writes blank rows to the target.
When you push the DATE_DIFF() function to Amazon Redshift using a Redshift ODBC connection, the Secure Agent incorrectly returns the difference values. If the result is positive, the Secure Agent returns negative values and if the result is negative, the positive value is returned.
When you configure a source filter under
Query Optionson any field in the source object, the Secure Agent converts boolean values to zero in the target object.
If you enter date and timestamp columns in the
SQL Querysource property, the mapping fails with the following error message:
The Secure Agent does not remove the external table names from the list of target objects available in the Target transformation.
When you select an Amazon Redshift ODBC connection as source and select an external table as a source object, the data preview fails.
If a field contains a Date or Datetime data type, the
Data Previewtab displays an offset value of +4 hours to the value of the field.
If you select the source type as query and do not map all the fields selected in the query in the
Field Mappingtab, the task fails with the following error message:
If you select the value of the
Operationtarget property as upsert and run a mapping, the Secure Agent performs an update operation instead of an upsert operation.
Workaround: To perform an upsert operation, select the appropriate option in the
Treat Source Rows Asadvanced target property.
Amazon Redshift V2 Connector does not support the key-range partitioning for a column of the Date/time data type.