On this Page
Table of Contents | ||||
---|---|---|---|---|
|
Snap type: | Write | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Description: | This Snap executes a Vertica bulk load. | ||||||||||||
Prerequisites: | None. | ||||||||||||
Support and limitations: | NoneDoes 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: |
| ||||||||||||
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 | Required. 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.
Example: public Default value: [None] | ||||||||||||
Table name | Required. The table on which to execute the insert operation.
Example: emp Default value: [None] | ||||||||||||
Create table if not present | Whether the table should be automatically created if not already present.
| ||||||||||||
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 | Required. The maximum number of rows that can fail before the bulk load operation is stopped. Example: 10 Default value: 0 | ||||||||||||
Truncate columns | Truncate column values that are larger than the maximum column length in the table. | ||||||||||||
Additional options | Additional options to be passed to the COPY command. See Copy Parameters for the available options. Default value: [None] | ||||||||||||
|
|
Note |
---|
Instead of building multiple Snaps with inter dependent DML queries, it is recommended to user the Multi Execute Snap. For example, when performing a create, insert and a delete function sequencially on a pipeline, using a Script Snap helps in create 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 name Temporary Files page Join
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|