Developer Workflow Guide

10.4.0
- 10.5.3
- 10.5.2
- 10.5
- 10.4.1

Back Next

Mapping Task Advanced Properties

The

Advanced

tab for a Mapping task includes properties that the task uses to run the mapping.

You can select values for the configuration properties. Or, you can assign a configuration property to task input. When you choose to assign the property to task input, you can assign a workflow parameter or a variable to the property. Assign a workflow or a variable to the property in the Mapping task

Input

tab. You can use a parameter set or a parameter file to change the value of the property.

You must select a value for the task recovery strategy. You cannot assign the task recovery strategy to task input.

Configure the following advanced properties for a Mapping task:

Task Recovery Strategy: Determines whether the Data Integration Service reruns or skips a task that is interrupted or that encounters an error. If the workflow is not enabled for recovery, the Data Integration Service ignores the task recovery strategy.; By default, the task has a restart recovery strategy.; When you use the Create Cluster task to create a cluster workflow, set the Mapping task recovery strategy to
Restart task
.
Cluster Identifier: Cluster Identifier string identifying the cluster where the Mapping task will run.; Set the Cluster Identifier property only for Mapping tasks that are contained in cluster workflows.; Choose one of the following options:; Value
Description

Blank (no value)

Run the mapping runs on the cluster configured in the Hadoop connection associated with the mapping.

AutoDeploy

Run the mapping on the cluster that the workflow creates.

When you choose this option, it also populates the Cluster Identifier property in the Create Cluster task with the value Set to AutoDeployCluster.

Default is AutoDeploy.

(Assign to task input)
Select this option to accept input from another source than the Create Cluster task. If you choose this option, enter a parameter value in the Cluster Identifier property of the Mapping task Input properties tab.
Default Date Time Format: The date time format that the Data Integration Services uses to convert data between date and string data types. Select one of the predefined formats, or type a valid date format string.

The property has a string datatype. Default is MM/DD/YYYY HH24:MI:SS.
Optimizer Level: Controls the optimization methods that the Data Integration Service applies to a mapping.

0 (None). The Data Integration Service does not optimize the mapping.
1 (Minimal). The Data Integration Service applies the early projection optimization method to the mapping.
2 (Normal). The Data Integration Service applies the early projection, early selection, pushdown, and predicate optimization methods to the mapping.
3 (Full). The Data Integration Service applies the early projection, early selection, pushdown, predicate, cost-based, and semi-join optimization methods to the mapping.

The property has an integer data type. Default is 2 (Normal).
High Precision: Runs the mapping with high precision.

High precision data values have greater accuracy. Enable high precision if the mapping produces large numeric values, for example, values with precision of more than 15 digits, and you require accurate values. Enabling high precision prevents precision loss in large numeric values.

The property has a boolean data type. Default is true.
Sort Order: The order in which the Data Integration Service sorts character data in the mapping.

The property has a string data type. Default is Binary.
Override Tracing Level: Sets the override tracing level used for each transformation in the mapping. The tracing level determines the amount of information that the Data Integration Service sends to the mapping log files.

Choose one of the following tracing levels:

none. The Data Integration Service does not override the tracing level that you set for each transformation.
terse. The Data Integration Service logs initialization information, error messages, and rejected data notifications.
normal. The Data Integration Service logs initialization information, status information, errors encountered, and skipped rows from transformation row errors. It summarizes mapping results, but not at the level of individual rows.
verboseInitialization. In addition to normal tracing, the Data Integration Service logs initialization details, the names of the index files and the data files, and detailed transformation statistics.
verboseData. In addition to verbose initialization tracing, the Data Integration Service logs each row that passes into the mapping. The Data Integration Service includes the names and the values of the parameters in the mapping run.The Data Integration Service also notes where it truncates string data to fit the precision of a column and it returns detailed transformation statistics. The Data Integration Service writes row data for all rows in a block when it processes a transformation.

The property has a string datatype. Default is normal.
Mapping Task Log Directory: Directory for the mapping task log. Use a directory local to the Data Integration Service to save the task log. If you do not enter a path, the Data Integration Service writes the log file to the directory from the LogDir system parameter. The default directory is
<Informatica installation directory>/tomcat/bin/disLogs/builtinhandlers
. An administrator can change this path in the Administrator tool. The system parameter is in the Data Integration Service service process properties.
Mapping Task Log File Name: Name of the mapping task log. You can enter a file name or the file name with the directory name in this field. The Data Integration Service appends the file name to the information in the
Masking Task Log File Directory
field. It appends the log file name to a UID and time stamp or to a mapping run number, based on how you choose to save the log file.
Java Classpath: The Java classpath to add to the beginning of the system classpath when the Data Integration Service runs the mapping task. Use this option if you use third-party Java packages, built-in Java packages, or custom Java packages in a Java transformation.
Mapping Task Log Save Type: Saves the Mapping task log file by timestamp or by the number of mapping task runs. The suffix of the mapping task log file name reflects the option you select.; When you configure a Mapping task log file, you can restrict the number of log files to keep at one time or you can choose to create an unlimited number of log files. Select one of the following save types:
Mapping task timestamp. Default. Saves log files by time stamp. The Integration Service saves an unlimited number of logs and labels them by time stamp. Each Mapping task log file name has the following format:
<MappingTaskLogFileName>_<UID>_<Timestamp>.log

Mapping task runs. Saves a specific number of Mapping task logs. Configure the number of log files to save in the
Save Mapping Task Logs for These Runs
property. Each Mapping task log file name has the following format:
<MappingTaskLogFileName>_<Run#>.log
Save Mapping Task Logs For These Runs: The number of log files to save when you save the log file by the number of mapping runs. Each log file name contains the run number. If you choose to save 10 Mapping task logs, the Data Integration Service saves logs numbered 0 to 9.

Value	Description
Blank (no value)	Run the mapping runs on the cluster configured in the Hadoop connection associated with the mapping.
AutoDeploy	Run the mapping on the cluster that the workflow creates. When you choose this option, it also populates the Cluster Identifier property in the Create Cluster task with the value Set to AutoDeployCluster. Default is AutoDeploy.
(Assign to task input)	Select this option to accept input from another source than the Create Cluster task. If you choose this option, enter a parameter value in the Cluster Identifier property of the Mapping task Input properties tab.