|
Function |
tMDMCommit explicitly commits all changes to the database made within the scope of a transaction in MDM. | |
|
Purpose |
This component is used to control the point in an MDM Job at which any changes made to the database within the scope of an MDM transaction are committed, for example to prevent partial commits if an error occurs. Note that if you need to commit each statement as an individual transaction, you have to use the Auto Commit function available in the connection component. | |
|
Component family |
Talend MDM | |
|
Basic settings |
Component List | Select the tMDMConnection component for which you want the commit action to be performed. |
|
|
Close Connection |
Select this check box to close the session for this connection to the MDM Server after committing 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 tMDM Connection, tMDMRollback. tMDMSP, tMDMViewSearch, tMDMInput, tMDMDelete, tMDMRouteRecord, tMDMOutput, and tMDMClose components. | |
For a related use case, see Scenario: Deleting master data from an MDM Hub.