Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

On this Page

Table of Contents
maxLevel2
excludeOlder Versions|Additional Resources|Related Links|Related Information

Snap type:

Write


Description:

This Snap executes a Vertica bulk load.
 

Prerequisites:

None.

Support and limitations:Does not work in Ultra Pipelines.
Account: 

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

Views:


InputThis Snap has exactly one input view.
OutputThis Snap has at most one output view.
Error

This Snap has at most one error view and produces zero or more documents in the view.

Note
Database Write Snaps output all records of a batch (as configured in your account settings) to the error view if the write fails during batch processing.



Settings

Label*


Specify 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*


Specify 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 retrieves available database schemas during suggest values.

Note

You can pass the values using Pipeline parameters but not upstream parameters.

Examplepublic

Default value: [None]

Table name*


Specify the table on which to execute the insert operation.

Note

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

Default value: None
Exampleemp

Create table if not present


Select this check box to automatically create the target table if it does not exist.

In the absence of a second input view (the schema/metadata document), the This Snap creates a table based on the data types of the columns generated from the first row of the input document (first input view).

Note

Due to implementation details, a newly created table is not visible to subsequent database Snaps during runtime validation. If you wish to immediately use the newly updated data you must use a child Pipeline that is invoked through a Pipeline Execute Snap.

Default value:  Not selected

Truncate data


Truncate the existing data before performing the data load. With the Bulk Update Snap, instead of executing truncate and then update, using a Bulk Insert Snap would be faster.

Default value:  Not selected

Maximum error count


Specify the maximum number of rows that can fail before the bulk load operation is stopped.

Default value0
Example: 10

Truncate columns


Truncate column values that are larger than the maximum column length in the table.
Default value:  Selected

Additional options


Additional options to be passed to the COPY command. See Copy Parameters for the available options.

Default value: [None]

Multiexcerpt include macro
nameSnap Execution
pageSOAP Execute

Multiexcerpt include macro
nameExecution_Detail_Write
pageSOAP Execute


Note

We recommend you to use Vertica - Multi Execute Snap, instead of building multiple Snaps with inter dependent DML queries.
In a scenario where the downstream Snap depends on the data processed on an upstream Database Bulk Load Snap, use the Script Snap to add delay for the data to be available.

For example, when performing a create, insert and a delete function sequentially on a Pipeline using a Script Snap helps in creating a delay between the insert and delete function or otherwise it may so happen that the delete function is triggered even before inserting the records on the table.

Multiexcerpt include macro
nameTemporary Files
pageJoin

Excerpt Include
Vertica Snap Pack
Vertica Snap Pack
nopaneltrue