Handling errors - 7.2

Data mapping

English (United States)
Talend Big Data Platform
Talend Data Fabric
Talend Data Management Platform
Talend Data Services Platform
Talend MDM Platform
Talend Real-Time Big Data Platform
Talend Studio
Data Governance > Third-party systems > Processing components (Integration) > Data mapping
Data Quality and Preparation > Third-party systems > Processing components (Integration) > Data mapping
Design and Development > Third-party systems > Processing components (Integration) > Data mapping

This scenario applies only to Talend Data Management Platform, Talend Big Data Platform, Talend Real Time Big Data Platform, Talend Data Services Platform, Talend MDM Platform and Talend Data Fabric.

For more technologies supported by Talend, see Talend components.

This following scenario creates a six-component Job that shows how to handle error conditions using the tHMap component.

When tHMap executes a Talend Data Mapper map, an ExecutionStatus object is always returned. A pointer to this object is stored in the globalMap as EXECUTION_STATUS. In addition, the Overall Severity numeric value (the constants are defined in ExecutionStatus) is also stored in the globalMap as EXECUTION_SEVERITY. Finally, a parameter called Execution Threshold is defined that specifies the severity on which to throw an exception, thus triggering Job-related or component-related error processing. The default value for this parameter is Fatal.

To consult the Javadoc for the ExecutionStatus object, see the Camel Runtime documentation included in the Talend Data Mapper runtime kits and the Talend Data Mapper User Guide.