Read

This Snap allows you to fetch data from a database by providing a table name and configuring the connection. The Snap produces the records from the database on its output view which can then be processed by a downstream Snap. 

ETL Transformations & Data Flow

This Snap enables the following ETL operations:

Fetch data from an existing Redshift table using the user configuration, and feed it to downstream Snaps.

JSON paths can be used in a query and will have values from an incoming document substituted into the query. However, documents missing values for a given JSON path will be written to the Snap's error view. After a query is executed, the query's results are merged into the incoming document overwriting any existing keys' values. The original document is output if there are no results from the query.

Queries produced by the Snap have an equivalent format:

If more powerful functionality is desired, then the Execute Snap should be used.

Input & Output

• Input: This Snap can have an upstream Snap that can pass a document output view such as Mapper or JSON Generator.
  
  

• Output: A document or a set of documents that contains the result of query for each input document. If no input document is provided, the query will be done only once.

None.

Works in Ultra Tasks.

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.

As of the March 2023 release, in the Redshift Select Snap, when you configure Output fields and deselect the Match data types checkbox, the display of the label name for the timestamptz data type in the output preview varies with the Redshift JDBC and the PostgreSQL JDBC drivers. For the Redshift JDBC driver, the Snap prefixes Redshift to the Timestamp label. For the PostgreSQL JDBC driver, Snap displays the labels as configured in the Snap settings. This does not impact the performance of the Snap.
Note: The behavior of the Snap remains the same when you select the Match data types checkbox, regardless of using the PostgreSQL or the Redshift driver—the label names are displayed as configured in the Snap settings.

Account and 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

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.

The database schema name. Selecting a schema filters the Table name list to show only those tables within the selected schema. The property is suggestible and will retrieve available database schemas during suggest values.

Required Name of table to execute insert on
Example: people

Where clause of select statement. This supports document value substitution (such as $person.firstname will be substituted with the value found in the incoming document at the path). However, you may not use a value substitution after "IS" or "is" word. Please see the examples below:

Examples: 

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

• email IS NOT NULL

• email IS NULL

Enter in the columns in the order in which you want to order by. The default database sort order will be used.

Example: 

name

email  

Starting row for the query.
Example: 0
Default value: [None] 

Number of rows to return from the query.
Example: 10

Default value: [None] 

Enter or select output field names for SQL SELECT statement. To select all fields, leave it at default.

Example: email, address, first, last, etc.

Default value: [None]

Default value: Not selected

If checked, the input document will be passed through to the output view under the key 'original'.

Default value: Selected

If selected, no document will be written to the output view when a SELECT operation does not produce any result. If this property is not selected and the Pass through property is selected, the input document will be passed through to the output view.

Default value: Not selected

Select one of the options for this property to override the state of the Auto commit property on the account. The Auto commit at the Snap-level has three values: True, False, and Use account setting. The expected functionality for these modes are:

•  True - The Snap will execute with auto-commit enabled regardless of the value set for Auto commit in the Account used by the Snap.

•  False - The Snap will execute with auto-commit disabled regardless of the value set for Auto commit in the Account used by the Snap.

• Use account setting - The Snap will execute with Auto commit property value inherited by the Account used by the Snap.

Default value: False

Specifies 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.

Example: 3

Default value: 0

Specifies the time interval between two successive retry requests. A retry happens only when the previous attempt resulted in an exception. 

Example:  10

Default value: 1

Conditional. This property applies only when the Output fields property is provided with any field value(s).

If this property is selected, the Snap tries to match the output data types same as when the Output fields property is empty (SELECT * FROM ...). The output preview would be in the same format as the one when SELECT * FROM is implied and all the contents of the table are displayed.

Default value: Not selected

Required when the value in the Number of retries field is greater than 0. 

Specify the location from the following options to store input documents between retries:

• In memory: The query results are stored in the Snaplex memory. If the query is too large to fit in the memory space, it may cause the Snap to fail, choose the On disk option.

• On disk: The query results are stored on the disk in a temporary (tmp) directory that is managed by the SnapLogic platform. This directory is deleted automatically when the Snap terminates.

Select an option to specify how the Snap must be executed. Available options are:

• Validate & Execute: Performs limited execution of the Snap (up to 50 records) during Pipeline validation; performs full execution of the Snap (unlimited records) during Pipeline execution.

• Execute only: Performs full execution of the Snap during Pipeline execution; does not execute the Snap during Pipeline validation.

• Disabled: Disables the Snap and, by extension, its downstream Snaps.

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.