By editing the write connector created, further info are required:
- Table Name : the name of the table to be written
- Write Strategy: The strategy to copy data into AWS. The "Full Load" strategy will replace the entire tables contents each time that the upstream transform has changed. If the upstream data set contains multiple Ascend partitions and not all partitions are expected to change on each update, then the "Incremental By Partition" strategy allows for Ascend to only update / insert / delete the partitions of the Amazon Redshift table that have changed in Ascend.
- A SQL Statement for Ascend to execute before writing: here the user has the possibility to execute a pre-processing script before writing to final table.
- A SQL Statement for Ascend to execute after writing: here the user has the possibility to execute a post-processing script after writing to final table.
Using a Staging Directory
While it is possible to write the Redshift without an S3 staging directory, we strongly recommend using the option as it uses Redshift's COPY command and improves write performance.
Updated 3 months ago