tHMap Standard properties - 7.0

Data mapping

EnrichVersion
7.0
EnrichProdName
Talend Big Data Platform
Talend Data Fabric
Talend Data Management Platform
Talend Data Services Platform
Talend MDM Platform
Talend Real-Time Big Data Platform
EnrichPlatform
Talend Studio
task
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

These properties are used to configure tHMap running in the Standard Job framework.

The Standard tHMap component belongs to the Processing family.

This component is available in 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.

Basic settings

Open Map Editor

Click the [...] button to open the tHMap Structure Generate/Select wizard where you can either have the hierarchical mapper structure generated automatically based on the schema, or select an existing hierarchical mapper structure. You must do this for both the input and output sides of your Map.

When you connect multiple output connections to the tHMap, the page displays a confirmation message that informs you that the mapper structures are generated based on the output connections.

If neither input nor output connection exists, the Structure Selection page is displayed.

Map Path

Specifies the map to be executed.

If the map was automatically created using the wizard described above, this is path is set automatically.

If you want to use an existing map, click the [...] button next to the Map Path field to open a dialog box in which you can select the map you want to use, then click the [...] button next to Open Map Editor to work with the map selected. Note that this map must have previously been created in the Mapping perspective.

Read Input As

Select the radio button which corresponds to how you want the input to be read. Depending on your map, only some of the options may be available.

  • Data Integration columns (default): Use this option if you are working with Talend Data Integration metadata.

  • Single column: Use this option if you are working with Talend Data Mapper metadata.

Write Output As

Select the radio button which corresponds to how you want the output to be written. Depending on your map, only some of the options may be available.

  • Data Integration columns (default): Use this option if you are working with Talend Data Integration metadata.

  • String (single column): Use this option if the data in the output column is to be a String.

  • Byte array (single column): Use this option if the data in the output column is to be a Byte array.

  • InputStream (single column): Use this option if you are working with Talend Data Mapper metadata and the input data is a stream.

  • Document (single column); Use this option if the output column is to be a Document.

    Note: If you have selected Document (single column) in the Job you created in versions 6.5 or below of Talend Studio and would like to import the same Job to versions 7.0 or onwards, ensure that you have updated the output representation of the map to XML prior to executing the Job. In versions 7.0 or onwards, the Document output type only applies to the XML representation.

Advanced settings

Map Variable

In this field, enter a context variable that you can use to define the relative path to a map file. For instance, if you enter ${context.mymapfile}, then mymapfile can point to different map files at runtime. This can be useful in cases where you want to use multiple maps without creating a new Job each time.

In the Contexts tab, the value must be an relative path. For instance, assuming you have a map called mapA in the folder Maps/FolderA, your context variable should contain the value "FolderA/mapA.xml". The .xml extension is needed because this is a reference to a file on the file system.

Note that all maps that might be referenced by the context variable must be present in the same Project. This way, when the job is built, it will contain all candidate maps and it will be possible to switch from one to another at runtime.

For further information on working with context variables, see Talend Studio User Guide.

Map each row (disable virtual component)

Select this check box to have tHMap process the input as a single output row. This prevents tHMap from buffering the input rows before delivering them downstream.

This can be useful, for example, when you use the tHMap component with tSAPIDocReceiver as the input component and any schema-aware component as the output component, because telling the tSAPIDocReceiver component to keep listening forever would otherwise lead to rows never being delivered.

Log Level

From the drop-down list, select how often you want events to be logged.

  • Infrequent: Logs only events related to startup, shutdown and exceptions.

  • Frequent (default): Logs events related to startup, shutdown and exceptions, and once per map execution.

  • Info: Logs all events at an informational level or higher.

  • All: Logs all events.

  • None: Logs nothing.

Exception Threshold

Talend Data Mapper returns an execution status with an severity value which can be OK, Info, Warning, Error or Fatal. By setting the exception threshold, you can specify the severity level at which an exception is thrown, thus enabling downstream components to detect the error in cases other than the default value of Fatal.

From the drop-down list, select the severity level at which an exception may be thrown during the execution of a map.

  • Fatal (default): An exception is thrown when a fatal error occurs.

  • Error: An exception is thrown when an error (or higher) occurs.

  • Warning: An exception is thrown when a warning (or higher) occurs.

Note that, in order to help you diagnose problems with your map, when you test the map in the Studio, any errors that occur which are at warning level or above will be printed in the console window, regardless of the setting of the Exception Threshold.

tStatCatcher Statistics

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

Global Variables

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.

EXECUTION_STATUS: the pointer to the ExecutionStatus object, which is returned whenever tHMap executes a Talend Data Mapper map. This is an After variable and it returns a string.

EXECUTION_SEVERITY: the Overall Severity numeric value. This is an After variable and it returns an integer.

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

Usage rule

tHMap is used for Jobs that require complex data mapping from a variety of different sources.

The input and output connections can use Talend Data Mapper metadata, Talend Data Integration metadata, or a combination of the two. Each connection is independent.

When you open the Map Editor for the first time for each connection, it either generates a Talend Data Mapper structure definition based on the schema of the Talend Data Integration component, or allows you to select an existing Talend Data Mapper structure if you are using Talend Data Mapper metadata. It then creates a map with the structure selected or generated.

This component can be used in several ways:

Note:
  • For further information about performing transformations using Talend Data Mapper , see Talend Data Mapper User Guide.
  • For tHMap using representations other than Hashmap, CSV, and Avro: Running tHMap may create temporary folders, which are not automatically removed after completing the Eclipse runtime. If you frequently run Talend Data Mapper, these files may pile up ad eventually lead to a disk full error. When the error occurs, the runtime fails. To avoid such scenario, ensure that you perform periodical cleaning.