tMDMRollback - 6.3

Talend Open Studio for Big Data Components Reference Guide

EnrichVersion
6.3
EnrichProdName
Talend Open Studio for Big Data
task
Data Governance
Data Quality and Preparation
Design and Development
EnrichPlatform
Talend Studio

Function

tMDMRollback returns a database to its original state before a Job was run, instead of committing any changes.

Purpose

This component is used as part of an overall MDM transaction to roll back any changes made in the database rather than definitively committing them, for example to prevent partial commits if an error occurs.

tMDMRollback properties

Component family

Talend MDM

 

Basic settings

Component List

Select the tMDMConnection component for which you want the rollback action to be performed.

 

Close Connection

Select this check box to close the session for this connection to the MDM Server after rolling back the changes. Note that even if you do not select this check box, the connection can still not be used in a subsequent subjob unless the Autocommit mode has been enabled.

Advanced settings

tStatCatcher Statistics

Select this check box to gather the processing metadata at the Job level as well as at each component level.

Global Variables

ERROR_MESSAGE: the error message generated by the component when an error occurs. This is an After variable and it returns a string. This variable functions only if the Die on error check box is cleared, if the component has this check box.

A Flow variable functions during the execution of a component while an After variable functions after the execution of the component.

To fill up a field or expression with a variable, press Ctrl + Space to access the variable list and choose the variable to use from it.

For further information about variables, see Talend Studio User Guide.

Usage

This component is to be used along with the tMDMConnection, tMDMCommit, tMDMSP, tMDMViewSearch, tMDMInput, tMDMDelete, tMDMRouteRecord, tMDMOutput, and tMDMClose components.

Related scenario

For a related use case, see Scenario: Deleting master data from an MDM Hub.