Table of Contents | ||||
---|---|---|---|---|
|
Snap type: | Write | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Description: | This Snap executes a Vertica bulk upsertVertica update. | ||||||||||||||
Prerequisites: | [None]N/A | ||||||||||||||
Support and limitations: | Ultra pipelines: Works in Ultra Pipelines .Spark mode: Not supported in Spark mode. | ||||||||||||||
Account: | This Snap uses account references created on the Accounts page of SnapLogic Manager to handle access to this endpoint. See Vertica Account for 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* | Truncate column values that are larger than the maximum column length in the table. | Required. The name of the table to execute the update operation on.
Example: emp Default value: [None] |
Note |
---|
Using this option creates a table with all columns of type STRING. |
Key columns
Required. The columns to use to check for existing entries in the target table.
Default value: [None]
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
Specify the SQL WHERE clause of the update statement. You can define specific values or columns to update (Set condition) in the upstream Snap, such as Mapper Snap, and then use the WHERE clause to apply these conditions on the columns sourced from the upstream Snap. For instance, here is a sample of an Update SQL query:
UPDATE table_name
SET column1 = value1, column2 = value2,
WHERE condition;
Info |
---|
If the Update Condition field is left blank, the condition is applied on all the records of the target table. |
Multiexcerpt include macro name Original structure_for_primary_key page Oracle - Update
Refer to the example to understand how to use the Update Condition.
Examples:
Without using expressions
EmpId = 12
email = 'you@example.com'
Using expressions
"EMPNO=$EMPNO and ENAME=$EMPNAME"
email = $email
emp=$emp
"emp='" + $emp + "'"
"EMPNO=" + $EMPNO + " and ENAME='" + $EMPNAME+ "'"
Warning | ||
---|---|---|
| ||
Using expressions that join strings together to create SQL queries or conditions has a potential SQL injection risk and is hence unsafe. Ensure that you understand all implications and risks involved before using concatenation of strings with '=' Expression enabled. |
The maximum number of times that the process must be retried before displaying an error.
Example: 2
Default value: 0
The maximum resting time in seconds between subsequent retries.
Example: 2
Default value: 1
Multiexcerpt include macro | ||||
---|---|---|---|---|
|
Multiexcerpt include macro | ||||
---|---|---|---|---|
|
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|