In this article

Overview

You can use the Redshift Execute Snap to execute arbitrary SQL queries. It executes DML (SELECT, INSERT, UPDATE, DELETE) type statements. This Snap works best with single queries.

Snap type

The Redshift Execute Snap is a Write-type Snap that writes the results of the executed SQL queries.

Prerequisites

Supported Redshift database environment and Redshift database account with valid access control.

Support for Ultra Pipelines

Works in Ultra Pipelines.

Limitations

If you use the PostgreSQL driver (org.postgresql.Driver) with the Redshift Snap Pack, it could result in errors if the data type provided to the Snap does not match the data type in the Redshift table schema. Either use the Redshift driver (com.amazon.redshift.jdbc42.Driver) or use the correct data type in the input document to resolve these errors.

When the SQL statement property is an expression, the pipeline parameters are shown in the suggest, but not the input schema.
Multiple queries might not work, because the underlying JDBC driver does not support multiple queries. We recommend you to use the Redshift - Multi Execute Snap for running multiple queries.

Behavior Change

In 4.26, when the stored procedures were called using the Database Execute Snaps, the queries were treated as write queries instead of read queries. So the output displayed message and status keys after executing the stored procedure.
In 4.27, all the Database Execute Snaps run stored procedures correctly, that is, the queries are treated as read queries. The output now displays message key, and OUT params of the procedure (if any). The status key is not displayed.
If the stored procedure has no OUT parameters then only the message key is displayed with value success.

If you have any existing Pipelines that are mapped with status key or previous description then those Pipelines will fail. So, you might need to revisit your Pipeline design.

As part of 436patches25696, when you use a stored procedure in the Redshift - Execute Snap, the Snap displays Message: Success and $UPDATE_COUNT=-1, 0, or 1 (based on the Snap Pack behavior) in the output.

Snap Views

Type

Format

Number of Views

Examples of Upstream and Downstream Snaps

Description

Input

Document

Min: 0
Max: 1

Mapper
JSON Generator

A Snap that can contain data that is to be used with the JSON paths defined in the SQL, if any, or to be passed through.

If the input view is defined, then the where clause substitutes incoming values for a specific query.

Output

Document

Min: 0
Max: 1

JSON Formatter

Mapper

A document with the result set output, if any, and update count as return status from the Redshift SQL. The Snap output all records of a batch (as configured in your account settings) to the error view if the write fails during batch processing.

If an output view is available and an update/insert/merge/delete statement was executed, then the original document that was used to create the statement will be output with the status of the executed statement.

Error

Error handling is a generic way to handle errors without losing data or failing the Snap execution. You can handle the errors that the Snap might encounter when running the Pipeline by choosing one of the following options from the When errors occur list under the Views tab:

Stop Pipeline Execution: Stops the current Pipeline execution when the Snap encounters an error.
Discard Error Data and Continue: Ignores the error, discards that record, and continues with the remaining records.
Route Error Data to Error View: Routes the error data to an error view without stopping the Snap execution.

Learn more about Error handling in Pipelines.

Snap Settings

Asterisk ( * ): Indicates a mandatory field.
Suggestion icon (): Indicates a list that is dynamically populated based on the configuration.
Expression icon ( ): Indicates the value is an expression (if enabled) or a static value (if disabled). Learn more about Using Expressions in SnapLogic.
Add icon ( ): Indicates that you can add fields in the field set.
Remove icon ( ): Indicates that you can remove fields from the field set.

Field Name	Field Type	Description
Label* Default Value: Redshift - Execute Example: Redshift - Execute	String	Specify the name for the Snap.
SQL statement* Default Value: N/A Example: `"SELECT""EMPNO=$EMPNO and ENAME=$EMPNAME"`	String/Expression	Specify the SQL statement to execute on the server. Redshift allows using \ (backslash) or ' (single quote) to escape special characters in the SQL. Therefore, we recommend that you use ' (single quote) in the SQL statement to escape special characters . We recommend you to add a single query in the SQL Statement field. Valid JSON paths that are defined in the WHERE clause for queries/statements are substituted with values from an incoming document. If the document is missing a value to be substituted into the query/statement, it will be written to the error view. If ‘$' is not part of the JSON path, it can be escaped by writing it as `\$` so that it can be executed as-is. For example, `SELECT \$2, \$3 FROM mytable`. If the character before `$` is alphanumeric, then `'$'` does not have to be escaped. (for instance, `SELECT metadata$filename` ...) Following is an example of the procedure: `CREATE OR REPLACE PROCEDURE sp_inout_proc (INOUT a int, b int, INOUT c int)` `AS \$\$` `BEGIN` `a := b * a;` `c := b * c;` `END;` `\$\$` If a SELECT query is executed, the query results are merged into the incoming document and any the values of the existing keys are overwritten. If there are no results from the query, the original document is written. If the SQL is parameterized (having valid JSON paths defined in the SQL text), the Snap creates a prepared statement and binds any parameters with the substituted values from the incoming document before executing in batch. If the SQL is not parameterized (literal SQL text), it will not create a PREPARE statement and instead execute SQL as a single query instead of batching. Learn more about executing SQL statements.
Query type Default Value: Auto Example: Read	Dropdown list/Expression	Select the type of query for your SQL statement (Read or Write). When Auto is selected, the Snap tries to determine the query type automatically. If the execution result of the query is not as expected, you can change the query type to Read or Write.
Pass through Default Value: Selected	Checkbox	Select this checkbox to pass the input document through to the output view under the key 'original'. This property applies only to the Execute Snaps with SELECT statement.
Ignore empty result Default Value: Deselected	Checkbox	Select this checkbox to ignore empty result; no document will be written to the output view when a SELECT operation does not produce any result. If you deselect this checkbox and select the Pass through checkbox, the input document will be passed through to the output view.
Number of retries Default Value: 0 Example: 3	Integer/Expression	Specify the maximum number of attempts to be made to receive a response. The request is terminated if the attempts do not result in a response. Ensure that the local drive has sufficient free disk space to store the temporary local file.
Retry interval (seconds) Default Value: 1 Example: 10		Specify the time interval between two successive retry requests. A retry happens only when the previous attempt resulted in an exception.
Auto commit Default Value: Use account setting Example: True	Dropdown list	Select one of the following options: True: The Snap enables the auto-commit. The value set on this field overrides the Auto commit property set at the account level. False: The Snap disables the auto-commit. The value set on this field overrides the Auto commit property set at the account level. Use account setting: The Snap uses the Auto commit value set in the Account. When you select this option, you must enable the Auto commit option in the account settings. Auto commit may be enabled for certain use cases if PostgreSQL JDBC driver is used in either Redshift, PostgreSQL or Generic JDBC Snap. But the JDBC driver may cause out of memory issues when Select statements are executed. For such cases, we recommend you to set Auto commit in the Snap settings to False and the Fetch size in the Account settings can be increased for optimal performance. Behavior of DML Queries in the Execute Snap when auto-commit is false DDL queries used in the Execute Snap is committed by the database itself, regardless of the Auto-commit setting. When Auto commit is set to false for the DML queries, the commit is called at the end of the Snap's execution. The Auto commit must be true in a scenario where the downstream Snap does depend on the data processed on an upstream Snap containing a DML query.
Snap Execution Default Value: Execute only Example: Validate & Execute	Dropdown list	Select one of the three modes in which the Snap executes. Available options are: Validate & Execute: Performs limited execution of the Snap, and generates a data preview during Pipeline validation. Subsequently, performs full execution of the Snap (unlimited records) during Pipeline runtime. Execute only: Performs full execution of the Snap during Pipeline execution without generating preview data. Disabled: Disables the Snap and all Snaps that are downstream from it.

Troubleshooting

Error	Reason	Resolution
`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.

Additional Information

Scenarios to successfully execute your SQL statements

Scenario 1: Executing SQL statements without expressions

When you deselect the expression toggle of the SQL statement field:

You must not embed the SQL statement within quotes.
The $<variable_name> parts of the SQL statement are expressions. In the below example, $id and $book.

email = 'you@example.com' or email = $email
emp=$emp

The JSON path is allowed only in the WHERE clause. If the SQL statement starts with SELECT (case-insensitive), the Snap regards it as a select-type query and executes once per input document. If not, it regards it as write-type query and executes in batch mode.

Scenario 2: Executing SQL queries with expressions

When you select the expression toggle of the SQL statement field:

The SQL statement must be within quotes.
The + $<variable_name> + parts of the SQL statement are expressions, and must not be within quotes. In the below example, $tablename.
The $<variable_name> parts of the SQL statement are bind parameter, and must be within quotes. In the below example, $id and $book.

Note: Table and column names must not be provided as bind parameters. Only values can be provided as bind parameters.

The non-expression form uses bind parameters, so it is much faster than executing N arbitrary SQL expressions.
Using expressions that join strings together to create SQL queries or conditions has a potential SQL injection risk and hence unsafe. Ensure that you understand all implications and risks involved before using concatenation of strings with '=' Expression enabled.
The '$' sign and identifier characters, such as double quotes (“), single quotes ('), or back quotes (`), are reserved characters and should not be used in comments or for purposes other than their originally intended purpose.

Single quotes in values must be escaped

Any relational database (RDBMS) treats single quotes (') as special symbols. So, single quotes in the data or values passed through a DML query may cause the Snap to fail when the query is executed. Ensure that you pass two consecutive single quotes in place of one within these values to escape the single quote through these queries. For example:

If String	To pass this value	Use
Has no single quotes	^{Schaum Series}	^{'Schaum Series'}
Contains single quotes	^{O'Reilly's Publication}	'`O''Reilly''s Publication`'

Recommendations

Be cautious when running your queries, because you can drop your database and lock tables while executing SQL statements.
Running multiple queries might not work with the Redshift - Execute Snap. If you need to run multiple queries, we recommend you to use the Redshift -Multi Execute Snap.

ETL Transformations and Data Flow

This Snap enables the following ETL operations/flows:

Extract data from an existing Redshift Table.
Transform any input document SnapLogic types to Redshift JDBC types for any input and transform any output document Redshift JDBC types to SnapLogic types for output.
Load data in the Redshift table.

The SQL (to be executed) is passed to Redshift. Here’s the detailed data flow:

The Snaps collects the user account information, and the SQL statement (after any expression evaluation), and any JDBC jars defined in the Redshift database account. JDBC jars defined in the Redshift database account are at customer discretion and should be Redshift approved/supported.
Valid JSON paths that are defined in the WHERE clause for queries/statements will be substituted with values from an incoming document as a prepared statement. The substituted values will be transformed from the SnapLogic type value to the appropriated JDBC type values based on the database's column type. If there are no JSON paths then a JDBC query will be utilized instead of a prepared statement.
Successful execution may create a result set. The result set columns will be transformed from the JDBC type value to the SnapLogic type value.
Data errors may occur, therefore an error view should be created to handle these conditions. If the batch has a data error the error data will be written to the error view and the rest of the batch will not be processed. However, a batch data error will not stop subsequent batches from executing.
Select SQLs will not use auto-commit. For non-select SQL, commit happens at successful batch completion when the database account has Auto commit enabled. If the database account does not have Auto commit enabled, commit happens at end of the successful Snap run. Therefore the Auto commit the setting must be configured to be processed in the desired way. For example, If a downstream Snap needs to see the data in the database, auto-commit should be enabled.
The database account uses a shared connection pool for efficiency and to prevent opening too many connections to a database. It is possible that another Snap with the same database account settings may be reusing the same connection as the Redshift Execute. To avoid reusing another Snap's connection for the purpose of isolating DML operations or debugging connection operations, use a different database account having different settings - this will cause the database connection to be unique to the Redshift Execute Snap.

Examples

Redshift - Execute Snap’s functionality as a standalone Snap in a pipeline

The use case requirement for this basic example is that we want to leverage the database query engine to provide uniqueness, a different output column, and a literal output value that the Redshift Select Snap cannot perform by itself. This example demonstrates how you can leverage other database query engine capabilities (functions, joins, and so on) and create more complex results than just getting filtered data out of a table.

Typical Snap Configurations

The key configuration of the Snap lies in how you pass the SQL statements.

Without Expression: Directly passing the required SQL statement in the Redshift Execute Snap.

JSON path example below, a statement is prepared and parameter values binded (from matching input document field) and executed using database account batch configuration of batch size 2. The JSON Generator preview shows the input values flowing into the Redshift Execute. The image at the right shows two output records. Note that only the input document with $name = "Danila" found a matching result in Redshift. The input document with $name = "Prasanna" was executed but returned no rows because the data was case sensitive and therefore did not match the database data value of "prassanna" . Because the Pass through checkbox was select and the original document is preserved in the output view.

The error view was enabled above so that processing can continue to end. Below is the error in the error output view.

With Expressions

An input document field named $tracked is used instead of hard coding "true" from the basic example above. An example value of $tracked is "'true'".

Pipeline Parameter: Pipeline parameter set to pass the required SQL Statement to the Redshift Execute Snap.

Same expression example, this time using pipeline parameter instead of an input document field reference.

Inserting Precision Numbers Into a Redshift Table

This example demonstrates how to use the Redshift Execute to insert precision numbers into a Redshift table using JSON Path expressions which will have the Redshift Execute create prepared statements, bind the input document field references, and execute using batching where the Redshift database account is configured with a batch size of 2. Below is a screenshot showing the more complex pipeline, the Redshift Execute configuration, and the inputs coming into the Redshift Execute.

The following image shows the error output view data:

Here is the regular output view data:

Executing a Stored Procedure

This example pipeline demonstrates how to call a stored procedure using the Redshift Execute Snap.

Create a store procedure sp_inout_proc as shown below. This stored procedure contains three values: a, b, and c.

On validating the Pipeline, the stored procedure is executed, and you can view only the status, message, and message description.

Next, we configure another Redshift Execute Snap to call the same sp_inout_proc stored procedure with these three values.

After validating the Pipeline, the Snap gets the values from the procedure and the output of the stored procedure is displayed as follows:

Downloads

Important steps to successfully reuse Pipelines

Download and import the Pipeline into SnapLogic.
Configure Snap accounts as applicable.
Provide Pipeline parameters as applicable.

	File	Modified

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.

No files shared here yet.

Drag and drop to upload or browse for files

Snap Pack History

Click to view/expand

Release	Snap Pack Version	Date	Type	Updates
May 2024	main26341	08 May 2024	Stable	Updated the Delete Condition (Truncates a Table if empty) field in the Redshift - Delete Snap to Delete condition (deletes all records from a table if left blank) to indicate that all entries will be deleted from the table when this field is blank, but no truncate operation is performed.
February 2024	main25112	14 Feb 2024	Stable	Updated and certified against the current SnapLogic Platform release.
November 2023	main23721	08 Nov 2023	Stable	Updated and certified against the current SnapLogic Platform release.
August 2023	main22460	16 Aug 2023	Stable	The Redshift-Bulk Load and Redshift-Bulk Upsert Snaps now support expression enablers for the Additional options field that enables you to use parameters. The Redshift - Execute Snap now includes a new Query type field. When Auto is selected, the Snap tries to determine the query type automatically. Behavior Change Starting with `version main22460`, in the Redshift Select Snap: When you create a table in Redshift, by default, all column names are displayed in lowercase in the output. When you enter column names in uppercase in the Output Field property, the column names are displayed in lowercase in the output.
May 2023	main21015	10 May 2023	Stable	Upgraded with the latest SnapLogic Platform release.
February 2023	432patches20500	17 Apr 2023	Latest	The Redshift Account no longer fails when a URL is entered in the JDBC URL field and no driver is specified.
February 2023	432patches20166	28 Mar 2023	Latest	Updated the description for S3 Security Token field as follows: Specify the S3 security token part of AWS Security Token Service (STS) authentication. It is not required unless a particular S3 credential is configured to require it.
February 2023	432patches20101	09 Mar 2023	Latest	The JDBC driver class for Redshift accounts is bundled with the com.amazon.redshift.jdbc42.Driver as the default driver. This upgrade is backward-compatible. The existing pipelines will continue to work as expected and the new pipelines will use the Redshift Driver as the default driver. SnapLogic will support providing fixes for the issues you might encounter with accounts that use the PostgreSQL driver only until November 2023. After November 2023, SnapLogic will not provide support for the issues with the PostgreSQL driver. Therefore, we recommend you to migrate from the PostgreSQL JDBC driver to the Redshift JDBC driver. Learn more about migrating from the PostgreSQL JDBC Driver to the Amazon Redshift Driver. (432patches20101) The Instance type option in the Redshift Bulk Load Snap enables you to use the Amazon EC2 R6a instance. This property appears only when the parallelism value is greater than one.
February 2023	432patches20035	07 Mar 2023	Latest	The Redshift Snaps that earlier supported only Redshift Cluster now support Redshift Serverless as well. With Redshift Serverless, you can avoid setting up and managing data warehouse infrastructure when you run or scale analytics.
February 2023	main19844	09 Feb 2023	Stable	Upgraded with the latest SnapLogic Platform release.
November 2022	main18944	10 Nov 2022	Stable	The Redshift - Insert Snap now creates the target table only from the table metadata of the second input view when the following conditions are met: The Create table if not present checkbox is selected. The target table does not exist. The table metadata is provided in the second input view.
August 2022	430patches17189	19 Aug 2022	Latest	The Redshift - Bulk Load and Redshift - Bulk Upsert Snaps now display relevant error message when the AWS security token is expired. The Redshift Account now validates correctly when the S3 bucket is blank.
August 2022	main17386	11 Aug 2022	Stable	The Redshift accounts support: Expression enabler to pass values from Pipeline parameters. Security Token for S3 bucket external staging.
4.29 Patch	429patches16908	28 Jul 2022	Latest	Enhanced the Redshift accounts with the following: Expression enabler to pass values from Pipeline parameters. Support for Security Token for S3 bucket external staging. Fixed an issue with Redshift - Execute Snap where the Snap failed when the query contained comments with single or double quotes in it. Now the Pipeline executes without any error if the query contains a comment.
4.29 Patch	429patches15806	08 Jun 2022	Latest	Fixed an issue with Redshift Account and Redshift SSL Account where the Redshift Snaps failed when the S3 Secret key or S3 Access-key ID contained special characters, such as +.
4.29	main15993	14 May 2022	Stable	Upgraded with the latest SnapLogic Platform release.
4.28	main14627	12 Feb 2022	Stable	Updated the label for Delete Condition to Delete Condition (Truncates Table if empty) in the Redshift Delete Snap.
4.27 Patch	427patches12999	20 Dec 2021	Latest	Fixed an issue with the Redshift Bulk Load Snap, where the temporary files in S3 were not deleted for aborted or interrupted Pipelines.
4.27 Patch	427patches12999	23 Nov 2021	Latest	Revised the field labels in Redshift Cross-Account IAM Role Account from: Cross-Account IAM Role ARN (Writing to Bucket) to S3 Bucket Write IAM Role ARN Cross-Account IAM properties (S3 Bucket) to S3 Bucket Read IAM Role. Removed Key/Trust Store Password and Key Alias fields in Redshift SSL and Redshift Cross-Account IAM Role SSL accounts.
4.27	main12833	13 Nov 2021	Stable	Enhanced the Redshift - Execute Snap to invoke stored procedures.
4.26	main11181	14 Aug 2021	Stable	Upgraded with the latest SnapLogic Platform release.
4.25 Patch	425patches11008	04 Aug 2021	Latest	Updated the AWS SDK from version 1.11.688 to 1.11.1010 in the Redshift Snap Pack and added a custom SnapLogic User Agent header value.
4.25	main9554	08 May 2021	Stable	Upgraded with the latest SnapLogic Platform release.
4.24	main8556	13 Feb 2021	Stable	Enhanced the Redshift - Select Snap to return only the selected output fields or columns in the output schema (second output view) using the Fetch Output Fields In Schema checkbox. If the Output Fields field is empty all the columns are visible. Added two accounts, Redshift Cross-Account IAM Role Account and Redshift Cross-Account IAM Role SSL Account to support Cross-Account IAM Role in Redshift Snaps.
4.23	main7430	14 Nov 2020	Stable	Fixed an issue with the Redshift Bulk Load Snap that fails while displaying a `Failed to commit transaction` error.
4.22	main6403	12 Sep 2020	Stable	Upgraded with the latest SnapLogic Platform release.
4.21 Patch	421patches6144	20 Jul 2020	Latest	Fixed the following issues with DB Snaps: The connection thread waits indefinitely causing the subsequent connection requests to become unresponsive. Connection leaks occur during Pipeline execution.
4.21 Patch	MULTIPLE8841	19 May 2020	Latest	Fixed the connection issue in Database Snaps by detecting and closing open connections after the Snap execution ends.
4.21	snapsmrc542	09 May 2020	Stable	Upgraded with the latest SnapLogic Platform release.
4.20 Patch	db/redshift8774		Latest	Fixed the Redshift - Execute Snap that hangs if the SQL statement field contains only a comment ("-- comment").
4.20	snapsmrc535	08 Feb 2020	Stable	Upgraded with the latest SnapLogic Platform release.
4.19 Patch	db/redshift8410	13 Dec 2019	Latest	Fixed an issue with the Redshift - Update Snap wherein the Snap is unable to perform operations when: An expression is used in the Update condition property. Input data contain the character '?'.
4.19	snaprsmrc528	14 Nov 2019	Stable	Upgraded with the latest SnapLogic Platform release.
4.18 Patch	db/redshift8043	14 Oct 2019	Latest	Enhanced the Snap Pack to support AWS SDK 1.11.634 to fix the NullPointerException issue in the AWS SDK. This issue occurred in AWS-related Snaps that had HTTP or HTTPS proxy configured without a username and/or password.
4.18 Patch	MULTIPLE7884	09 Oct 2019	Latest	Fixed an issue with the PostgreSQL grammar to better handle the single quote characters.
4.18 Patch	MULTIPLE7778	28 Aug 2019	Latest	Updated the AWS SDK library version to default to Signature Version 4 Signing process for API requests across all regions.
4.18	snapsmrc523	10 Aug 2019	Stable	Upgraded with the latest SnapLogic Platform release.
4.17 Patch	db/redshift7433	20 Jun 2019	Latest	Fixed an issue with the Redshift Bulk Load Snap wherein the Snap fails to copy the entire data from source to the Redshift table without any statements being aborted.
4.17	ALL7402	11 Jun 2019	Latest	Pushed automatic rebuild of the latest version of each Snap Pack to SnapLogic UAT and Elastic servers.
4.17	snapsmrc515	11 Jun 2019	Latest	Fixed an issue with the Redshift Execute Snap wherein the Snap would send the input document to the output view even if the Pass through field is not selected in the Snap configuration. With this fix, the Snap sends the input document to the output view, under the key original, only if you select the Pass through field. Added the Snap Execution field to all Standard-mode Snaps. In some Snaps, this field replaces the existing Execute during preview checkbox.
4.16 Patch	db/redshift6821	22 Feb 2019	Latest	Fixed an issue with the Lookup Snap passing data simultaneously to output and error views when some values contained spaces at the end.
4.16	snapsmrc508	16 Feb 2019	Stable	Upgraded with the latest SnapLogic Platform release.
4.15 Patch	db/redshift6286	06 Dec 2018	Latest	Fixed an issue with the Bulk Upsert Snap wherein there was no output for any input schema.
4.15 Patch	db/redshift6334	05 Dec 2018	Latest	Replaced Max idle time and Idle connection test period properties with Max life time and Idle Timeout properties, respectively, in the Account configuration. The new properties fix the connection release issues that were occurring due to default/restricted DB Account settings.
4.15	snapsmrc500	15 Dec 2018	Stable	Upgraded with the latest SnapLogic Platform release.
4.14 Patch	db/redshift5786	19 Sep 2018	Latest	Fixed an issue wherein the Redshift Upload snap logged the access and secret keys without encryption in the error logs. The keys are now masked.
4.14 Patch	db/redshift5667	13 Aug 2018	Latest	Added "Validate input data" property in the Redshift Bulk Load Snap to enable users to troubleshoot input data schema. Enhanced a check to identify whether the Provided Query in the Redshift Execute Snap is of read or write type.
4.14	snapsmrc490	11 Aug 2018	Stable	Upgraded with the latest SnapLogic Platform release.
4.13 Patch	db/redshift/5303	21 Jun 2018	Latest	Added a new property "Validate input data" in the Redshift Bulk Load Snap to help users troubleshoot the input data schema.
4.13 Patch	db/redshift5186	13 May 2018	Latest	Fixed the Bulk Load and Unload Snaps wherein the KMS encryption type property is failing with validation error.
4.13	snapsmrc486	12 May 2018	Stable	Added KMS encryption support to these Snaps: Redshift Unload, Redshift Bulk Load, Redshift Bulk Upsert, and Redshift S3 Upsert.
4.12 Patch	db/redshift5027	13 Apr 2018	Latest	Fixed an issue wherein the Redshift Snaps timeout and fail to retrieve a database connection.
4.12 Patch	MULTIPLE4967	05 Apr 2018	Latest	Provided an interim fix for an issue with the Redshift accounts by re-registering the driver for each account validation. The final fix is being shipped in a separate build.
4.12 Patch	MULTIPLE4744	27 Feb 2018	Latest	Added support for Redshift grammar to recognize window functions as being part of the query statement.
4.12	snapsmrc480	17 Feb 2018	Stable	Upgraded with the latest SnapLogic Platform release.
4.11 Patch	db/redshift4589	26 Jan 2018	Latest	Fixed an issue when creating a Redshift table via the second/metadata input view for the Redshift Bulk Load Snap.
4.11	snapsmrc465	11 Nov 2017	Stable	Added SSL support to the Configuring Redshift Accounts.
4.10 Patch	db/redshift4115	12 Oct 2017	Latest	The Upsert or BulkUpdate/BulkLoad shall not execute and produce output when no inputView has been provided.
4.10 Patch	redshift3936	14 Sep 2017	Latest	Addressed an issue in Redshift Execute with a Select that hangs after extracting 13 million in the morning or 30 million in the evening
4.10	snapsmrc414	12 Aug 2017	Stable	Added Auto commit property to the Select and Execute Snaps at the Snap level to support overriding of the Auto commit property at the Account level.
4.9.0 Patch	redshift3229	07 Jul 2017	Latest	Addressed an issue in Redshift Multiple Execute where INSERT INTO SELECT statement generated a 'transaction, commit and rollback statements are not supported' exception.
4.9.0 Patch	redshift3073	01 Jun 2017	Latest	Fixed an issue regarding connection not closed after login failure; Expose autocommit for "Select into" statement in PostgreSQL Execute Snap and Redshift Execute Snap
4.9	snapsmrc405	13 May 2017	Stable	Updated the Bulk Load, Bulk Upsert and S3 Upsert Snaps with the properties Vacuum type & Vacuum threshold (%) (replaced the original Vacuum property). Update the S3 Upsert Snap with the properties, IAM role and Server-side encryption to support data upsert across two VPCs. Added support for the Redshift driver under the account setting for JDBC jars.
4.8.0 Patch	redshift2852	10 Apr 2017	Latest	Addressed an issue with Redshift Insert failing with 'casts smallint as varchar' Addressed an issue with Redshift Bulk Upsert fails to drop temp table
4.8.0 Patch	redshift2799	28 Mar 2017	Latest	Addressed an issue with Redshift Snaps with the default driver failing with could not load JDBC driver for url file. Added the properties, JDBC Driver Class, JDBC jars and JDBC Url to enable the users to upload the Redshift JDBC drivers that can override the default driver.
4.8.0 Patch	redshift2758	27 Mar 2017	Latest	Potential fix for JDBC deadlock issue.
4.8.0 Patch	redshift2713	01 Mar 2017	Latest	Fixed Redshift Snap Pack rendering dates that are one hour off from the date returned by database query for non-UTC Snaplexes
4.8.0 Patch	redshift2697	22 Feb 2017	Latest	Addresses an issue where some changes made in the platform patch MRC294 to improve performance caused Snaps in the listed Snap Packs to fail.
4.8	snapsmrc398	11 Feb 2017	Stable	Redshift MultiExecute Snap introduced in this release. Redshift Account: Info tab added to accounts. Database accounts now invalidate connection pools if account properties are modified and login attempts fail. Info tab added to accounts. Database accounts now invalidate connection pools if account properties are modified and login attempts fail.
4.7.0 Patch	redshift2434	10 Jan 2017	Latest	Replaced newSingleThreadExecutor() with a fixed thread pool.
4.7.0 Patch	redshift2387	06 Jan 2017	Latest	Addressed an issue in Redshift Bulk Load Snap where Load Empty String was setting not working after release.
4.7.0 Patch	redshift2223	05 Dec 2016	Latest	Auto-commit is turned off automatically for SELECT
4.7.0 Patch	redshift2201	28 Nov 2016	Latest	Fixed an issue for database Select Snaps regarding Limit rows not supporting an empty string from a pipeline parameter.
4.7	snapsmrc382	23 Nov 2016	Stable	Updated the Redshift Snap Account Settings with the IAM properties that include AWS account ID , IAM role name, and Region name. Redshift Bulk Load Snap updated with the properties IAM Role & Server-side encryption. Redshift Bulk Upsert Snap updated with the properties Load empty strings, IAM Role & Server-side encryption. Updated the Redshift Upsert Snap with Load empty strings property. Updated the Redshift Unload Snap with the property IAM role.
4.6	snapsmrc362	13 Aug 2016	Stable	Redshift Execute Snap enhanced to fully support SQL statements with/without expressions & SQL bind variables. Resolved an issue in Redshift Execute Snap that caused errors when executing a command Select current_schemas(true). Resolved an issues in Redshift Execute Snap that caused errors when a Select * from <table_name> into statement was executed. Enhanced error reporting in Redshift Bulk Load Snap to provided appropriate resolution messages.
4.5.1	redshift1621	18 May 2016	Latest	Redshift S3 Upsert Snap introduced in this release. Resolved an issue that occurred while inserting mismatched data type values in Redshift Insert Snap.
4.5	snapsmrc344	18 May 2016	Stable	Resolved an issue in Redshift Bulk Upsert Snap that occurred when purging temp tables. Resolved an issue in Redshift Upload/Upsert Snap that occurred when using IAM credentials in an EC2 instance with an S3 bucket.
4.4.1	NA	18 Mar 2016	Latest	Resolved an issue with numeric precision when trying to use create table if not present in Redshift Insert Snap.
4.4	NA	13 Feb 2016	Stable	Upgraded with the latest SnapLogic Platform release.
4.3.2	NA	15 Jan 2016	Stable	Redshift Select Where clause property now has expression support. Redshift Update Update condition property now has expression support. Resolved an issue with Redshift Select Table metadata being empty if the casing is different from the suggested one for table name
4.3	NA	24 Oct 2015	Stable	Table List Snap: A new option, Compute table graph, now lets you determine whether or not to generate dependents data into the output. Redshift Unload Snap Parallel property now explicitly adds 'PARALLEL [OFF\|FALSE]' to the UNLOAD query.
4.2	NA	07 Aug 2015	Latest	Resolved an issue where Redshift SCD2 Snap historized the current row when no Cause-historization fields had changed. Ignore empty result added to Execute and Select Snaps. The option will not any document to the output view for select statements. Resolved an issue with Redshift Select Snap returning a Date object for DATE column data type instead of a LocalDate object. Resolved an issue in RedShift SCD2 failing to close database cursor connection. Resolved an issue with Redshift Lookup Snap not handling values with spaces in the prefix. Updated driver not distributed with the Redshift Snap Pack. Output fields table property added to Select Snap. Resolved an issue with Redshift - Bulk Loader incorrectly writing to wrong location on S3 and disable data compression not working Resolved an issue in Execute and Select Snaps where the output document was the same as the input document if the query produces no data. When there is no result from the SELECT query, the input document will be passed through to the output view as a value to the 'original' key. The new property Pass through with true default.
NA	NA	02 May 2015	NA	Redshift Account: Enhanced error messaging Redshift SCD2: Bug fixes with compound keys RedShift Lookup: Bug fixes on lookup failures; Pass-though on no lookup match property added to allow you to pass the input document through to the output view when there is no lookup matching.