Write

This Snap is used to execute multiple Redshift SQL statements sequentially inside of a single BEGIN and END transaction for each input document. If an SQL statement fails, subsequent SQL statements are not executed and error output goes to the error view (if the corresponding option is selected). If all statements are successful, all output results go to the output view. Data can be written to both output and error view if using multiple input documents. Use this Snap to perform updates to Redshift data that would otherwise be done in a Stored Procedure.

ETL Transformations & Data Flow

This Snap enables the following ETL operations/flows:

The Snap executes a sequence of multiple Redshift DDL commands in a sequential order as specified in the Executions section and the result will be written to the output view which contains results from individual queries that have been executed from the provided properties. If any submitted query fails, the Snap will throw an exception and rollback changes from prior queries.

Input & Output:

• Input: The Snap can have zero to one input document to trigger multi-executions of SQL statements and any necessary field data values if expressions are used in the SQL executions.

• Output: The output results will be written to the output view. 

Upstream & Downstream Snaps

• Expected Upstream Snaps: Upstream Snap is not required - the MultiExecute Snap will execute once if no input view is defined. However, if there is an upstream Snap, it should only produce documents to trigger the MultiExecute Snap. For example, if zero documents are produced by an upstream Snap, the MultiExecute SQL will not execute. If two documents are produced, the MultiExecute will execute twice, once for each input document (the original input document data will be preserved in the output views) 

• Expected Downstream Snaps: Applicable downstream Snaps to handle the possible Redshift SQL data results emitted on the output and error view can be used.

None

• Works in Ultra Tasks.

• SELECT statements are not accepted for execution.

• Does not support transaction, commit, and rollback operations.

Account & Access

This Snap uses account references created on the Accounts page of SnapLogic Manager to handle access to this endpoint. See Redshift Account for information on setting up this type of account.

Views

[None]

Required. The name for the Snap. You can modify this to be more specific, especially if you have more than one of the same Snap in your pipeline.

Required. Specifies the SQL statement to execute on the server.  

Examples: 

• create table stage_table as select * from leads l where l.value not in (select h.value from leads_hist h);

• insert into leads_hist select * from stage_table;

• drop table stage_table; 

Default value: [None]

type "e" does not exist

This issue occurs due to incompatibilities with the recent upgrade in the Postgres JDBC drivers.

Download the latest 4.1 Amazon Redshift driver here and use this driver in your Redshift Account configuration and retry running the Pipeline.