Page Comparison

Snap type:

Read

Description:

This Snap provides the ability to look up records in the target table and return a selected set of fields for every matched record. The Snap executes one request per multiple input documents to avoid making a request for every input record.

JSON paths can be used in the Snap properties and will have values from an incoming document substituted into the properties. 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.

Queries produced by the Snap have the format:

Code Block

SELECT [Output fields] FROM [Table name] WHERE
[C1 = V11 AND C2 = V21 AND...[Cn = Vn1] OR
[C1 = V12 AND C2 = V22 AND...[Cn = Vn2] OR 
......................................  OR
[Cn = V1n AND Cm = V2m AND...[Cn = Vnm]

The Snap ignores any duplicated lookup condition in the input document stream since it maintains a cache for lookup conditions internally.

Expected upstream Snaps: Any Snap that produces documents in the output view such as CSV Parser, JSON Parser, Structure, Data.

Expected downstream Snaps: Any Snap that receives documents in the input view such as JSON Formatter, Structure, Data. The CSV Formatter will cause an error because the output data is not flattened Map data.

Expected input: Each document in the input view should contain Map data of key-value entries. Input data might contain values needed to evaluate expressions in the Object type, the Output fields, and the Conditions properties. If the Pass-though on no lookup match property is unchecked, please make sure input data types match column data types in the database table. Otherwise, you may encounter an error message "Cannot find an input data which is related to the output record .....". If the error view is open, all input data in the batch are routed to the error view with the same error information.

Expected output: Each document in the output view contains Map data of key-value entries, where keys are the Output fields property values. The input data that has produced the corresponding output data is also included in the output data under the original key.

Prerequisites:

N/A

Support and limitations:

Works in Ultra Task Pipelines.

Account:

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

Views:

Input	This Snap has exactly one input view and expects documents in the view. Each document should have values for one AND clause in the WHERE statement.
Output	This Snap has exactly one output view and produces documents in the view. The output document includes the corresponding input data under the original key. If there is no results from the query, each output field will have a null value.
Error	This Snap has at most one error view and produces zero or more documents in the view.

Settings

Label

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.

Schema name

The database schema name. Selecting a schema filters the Table name list to show only those tables within the selected schema.

Note
The values can be passed using the pipeline parameters but not the upstream parameter.

Table name

Required. Enter or select the name of SQL table on which to execute the lookup query.

Note
The values can be passed using the pipeline parameters but not the upstream parameter.

Example: people

Output fields

Required. Enter or select output field names for the SQL SELECT statement. If this property is empty, the Snap selects all fields by executing the statement "SELECT * FROM ...".
Example: email, address, first, last

Lookup conditions

Required. The lookup conditions are created by using the lookup column name and the lookup column value. Each row will build a condition, such as lookupColumn1 = $inputField. Each additional row will be concatenated using a logical AND. All rows together build the lookup condition being used to lookup records in the lookup table.

Value

Required. Enter or select the JSON path of the lookup column value. The value will be provided by the input data field.
Example:$email, $first, $last

Lookup column name

Required. Enter or select lookup column name.
Example: email, first, last

Pass-through on no lookup match

When there is no lookup matching an input document, the input document will pass through to the output view if this property is checked. Otherwise, it will be written to the error view as an error condition.

Default value: Not selected

Number of retries

The maximum number of times that the process must be retried before displaying an error.

Example: 2

Default value: 0

Retry interval (seconds)

The maximum resting time in seconds between subsequent retries.

Example: 2

Default value: 1

Multiexcerpt include macro

name	Snap Execution
page	Anaplan Read

Multiexcerpt include macro

name	Snap_Execution_Introduced
page	Anaplan Read

Note

Date type column cannot used in the Lookup conditions. You will have to use the Oracle Execute Snap for this purpose. An example of the execute statement is:

Code Block
SELECT * FROM LOOKUPTABLE WHERE DATECOL >= TO_DATE('2014-11-03', 'yyyy-mm-dd')

Please note ">=" is used instead of "=" in the WHERE clause. If you use "=", you will not get any res

Insert excerpt

	Vertica Snap Pack
	Vertica Snap Pack
nopanel	true

Versions Compared

Old Version 11

New Version Current

Key

Settings