This Snap has exactly one document input view.

The columns of the selected table need to be mapped upstream using a Mapper Snap. The Mapper Snap will provide the target schema, which reflects the schema of the table that is selected for the Merge Snap.

Expected input: Document that conforms to the input view schema of the Snap. The input view schema is provided to an upstream Mapper Snap based on the selected service object.

• Mapper

This Snap has at most one output view.

If an output view is available, then the original document that was used to create the statement will be output with the status of the merge executed.

Expected output: Document which represents the status of the merge operation for that document. Each merge operation is represented as one document in the output view.

• Mapper

Label

Required. Specify a unique name for the Snap. Modify this to be more appropriate, especially if more than one of the same Snaps is in the pipeline.

Default value: Oracle - Merge

Specify the database schema name. The suggestions in the Schema field are populated only when at least a single table exists in the schema. If no tables exist to use that schema, only SYS, SYSTEM, and XDB are populated.

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

Example: SYS

Default value: None

Required. Specify the table that the rows will be inserted into. This list is populated based on the tables associated with the selected schema.

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

Example: people

Default value: None

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

When you enable retry and a connection failure occurs that cannot be recovered by retry, the Snap writes a connection failure error in the error view. In some cases, the error view records might contain duplicate data that was written to the database. Ensure to verify all the records in the error file before you restart the merge request. You can locate the duplicate records in the error view by checking the $reason property for the sub-string: Connection is not available, request timed out.

Example: 3

Default value: 0

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

When you enable retry and a connection failure occurs that cannot be recovered by retry, the Snap writes a connection failure error in the error view. In some cases, the error view records might contain duplicate data that was written to the database. Ensure to verify all the records in the error file before you restart the merge request. You can locate the duplicate records in the error view by checking the $reason property for the sub-string: Connection is not available, request timed out.

Example: 10

Default value: 1

Required. The ON condition of the merge statement. A boolean-type expression is expected. For an explanation of merge syntax, see Oracle Merge.

Default value: None

Snap execution

Default value: Execute only

Example: Validate & execute