Data Engineering Integration
All Products
Transformation
| Rules and Guidelines
|
---|---|
Transformations not listed in this table are not supported. | |
Address Validator
| The Address Validator transformation cannot generate a certification report.
|
Aggregator
| Mapping validation fails in the following situations:
When a mapping contains an Aggregator transformation with an input/output port that is not a group by port, the transformation might not return the last row of each group with the result of the aggregation. Hadoop execution is distributed, and thus it might not be able to determine the actual last row of each group.
|
Case Converter
| Supported without restrictions.
|
Comparison
| Supported without restrictions.
|
Consolidation
| The Consolidation transformation might process data differently in the native environment and in a Hadoop environment.
The transformation might demonstrate the following differences in behavior:
|
Data Masking
| Mapping validation fails in the following situations:
|
Data Processor
| Mapping validation fails in the following situations:
|
Decision
| Supported without restrictions.
|
Expression
| Mapping validation fails in the following situations:
An Expression transformation with a user-defined function returns a null value for rows that have an exception error in the function.
|
Filter
| Supported without restrictions.
|
Java
| You must copy external .jar files that a Java transformation requires to the Informatica installation directory in the Hadoop cluster nodes at the following location:
[$HADOOP_NODE_INFA_HOME]/services/shared/jars You can optimize the transformation for faster processing when you enable an input port as a partition key and sort key. The data is partitioned across the reducer tasks and the output is partially sorted.
The following restrictions apply to the Transformation Scope property:
You can enable the Stateless advanced property when you run mappings in a Hadoop environment.
The Java code in the transformation cannot write output to standard output when you push transformation logic to Hadoop. The Java code can write output to standard error which appears in the log files.
|
Joiner
| Mapping validation fails in the following situations:
|
Labeler
| Supported without restrictions.
|
Lookup
| Mapping validation fails in the following situations:
Mappings fail in the following situations:
If you add a data object that uses Sqoop as a Lookup transformation in a mapping, the Data Integration Service does not run the mapping through Sqoop. It runs the mapping through JDBC.
When you a run mapping that contains a Lookup transformation, the Data Integration Service creates lookup cache .jar files. Hive copies the lookup cache .jar files to the following temporary directory: /tmp/<user_name>/hive_resources . The Hive parameter
hive.downloaded.resources.dir determines the location of the temporary directory. You can delete the lookup cache .jar files specified in the LDTM log after the mapping completes to retrieve disk space.
|
Match
| Mapping validation fails in the following situations:
A Match transformation generates cluster ID values differently in native and Hadoop environments. In a Hadoop environment, the transformation appends a group ID value to the cluster ID.
|
Merge
| Supported without restrictions.
|
Parser
| Supported without restrictions.
|
Rank
| Mapping validation fails in the following situations:
|
Router
| Supported without restrictions.
|
Sorter
| Mapping validation fails in the following situations:
The Data Integration Service logs a warning and ignores the Sorter transformation in the following situations:
The Data Integration Service treats null values as high, even if you configure the transformation to treat null values as low.
|
Standardizer
| Supported without restrictions.
|
SQL
| Mapping validation fails in the following situations:
|
Union
| Supported without restrictions.
|
Update Strategy
| Mapping validation fails in the following situations:
The mapping fails in the following situations:
Compile validation errors occur and the mapping execution stops in the following situations:
The Hive engine performs Update as Update even if the transformation is configured to Update as Insert or Update else Insert.
When the Update Strategy transformation receives multiple update rows for the same key, the results might differ.
|
Weighted Average
| Supported without restrictions.
|
Transformations not listed in this table are not supported. |
Updated July 03, 2018