AlloyDB Update

In this article

Overview

You can use this Snap to execute an AlloyDB update with the given properties. 

Updates are batched up until the account's batch size property or the structure of the update statement changes. An update statement will change if an incoming document contains different keys than a previous document. 

Snap Type

The AlloyDB Update Snap is a Write-type Snap.

Prerequisites

None.

Support for Ultra Pipelines

Works in Ultra Task Pipelines.

Limitations and Known Issues

None.

Snap Views

 

Type

Format

Number of Views

Examples of Upstream and Downstream Snaps

Description

Type

Format

Number of Views

Examples of Upstream and Downstream Snaps

Description

Input 

Document

 

  • Min: 1

  • Max: 1

  • Mapper

  • Oracle Execute

Schema name, table name, and the update condition to apply on the query.

Output

Document

  • Min: 0

  • Max: 1

  • File Writer

  • Mapper

Keys from the document are used as the columns to update, and their values are the updated values in the column.

Error

Error handling is a generic way to handle errors without losing data or failing the Snap execution. You can handle the errors that the Snap might encounter while running the Pipeline by choosing one of the following options from the When errors occur list under the Views tab:

  • Stop Pipeline Execution: Stops the current Pipeline execution if the Snap encounters an error.

  • Discard Error Data and Continue: Ignores the error, discards that record, and continues with the remaining records.

  • Route Error Data to Error View: Routes the error data to an error view without stopping the Snap execution.

Learn more about Error handling in Pipelines.

Snap Settings

  • Asterisk ( * ): Indicates a mandatory field.

  • Suggestion icon (): Indicates a list that is dynamically populated based on the configuration.

  • Expression icon ( ): Indicates the value is an expression (if enabled) or a static value (if disabled). Learn more about Using Expressions in SnapLogic.

  • Add icon ( ): Indicates that you can add fields in the field set.

  • Remove icon ( ): Indicates that you can remove fields from the field set.

  • Upload icon ( ): Indicates that you can upload files.

Field Name

Field Type

Description

Field Name

Field Type

Description

Label*

String

Specify a unique name for the Snap.

 

Schema name

 

Default value: None
Example: myschema

 

String/Expression/Suggestion

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

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

Table name*

 

Default Value: None
Example: people

String/Expression/Suggestion

The name of the table to execute the update operation on.

 

Update condition

 

Default value: None
Examples: 

Without using expressions

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

  • emp=$emp

Using expressions

  • "EMPNO=$EMPNO and ENAME=$EMPNAME"

  • "emp='" + $emp + "'"

  • "EMPNO=" + $EMPNO + " and ENAME='" + $EMPNAME+ "'"

String/Expression

Condition to execute an update on.

Number of retries

Default value: 0
Example: 3

 

Integer/Expression

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

Retry interval (seconds)

Default value: 1
Example:  10

Integer/Expression

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

Snap Execution

Default Value:  Execute Only
Example: Validate & Execute

Dropdown list

Select one of the following three modes in which the Snap executes:

  • Validate & Execute: Performs limited execution of the Snap, and generates a data preview during Pipeline validation. Subsequently, performs full execution of the Snap (unlimited records) during Pipeline runtime.

  • Execute only: Performs full execution of the Snap during Pipeline execution without generating preview data.

  • Disabled: Disables the Snap and all Snaps that are downstream from it.

Snap Pack History

Related Links

Â