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.
|
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. When a mapping contains a Filter transformation on a partitioned column of a Hive source, the Blaze engine can read only the partitions that contain data that satisfies the filter condition. To push the filter to the Hive source, configure the Filter transformation to be the next transformation in the mapping after the source.
|
Java
| To use external .jar files in a Java transformation, perform the following steps:
|
Joiner
| Mapping validation fails in the following situations:
Map-side join is disabled when the Joiner transformation is configured for detail outer join or full outer join.
|
Key Generator
| Supported without restrictions.
|
Labeler
| Supported without restrictions.
|
Lookup
| Mapping validation fails 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.
|
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.
|
Normalizer
| Supported without restrictions.
|
Parser
| Supported without restrictions.
|
Rank
| Supported without restrictions.
|
Router
| Supported without restrictions.
|
Sequence Generator
| Mapping validation fails in the following situations:
If you want the Data Integration Service to reset the sequence data object to the start value for each mapping run, then you must run the mapping in the native environment.
|
Sorter
| The Blaze engine can perform global sorts when the following conditions are true:
If any of the conditions are not true, the Blaze engine performs a local sort.
Mapping validation fails in the following situations:
|
Standardizer
| Supported without restrictions.
|
Union
| Supported without restrictions.
|
Update Strategy
| The Update Strategy transformation is supported only on Hadoop distributions that support Hive ACID.
Mapping validation fails in the following situations:
The mapping fails in the following situation:
Compile validation errors occur and the mapping execution stops in the following situations:
To use a Hive target table with an Update Strategy transformation, you must create the Hive target table with the following clause in the Hive Data Definition Language:
TBLPROPERTIES ("transactional"="true") .
To use an Update Strategy transformation with a Hive target, verify that the following properties are configured in the hive-site.xml configuration set associated with the Hadoop connection:
If the Update Strategy transformation receives multiple update rows for the same primary key value, the transformation selects one random row to update the target.
If multiple Update Strategy transformations write to different instances of the same target, the target data might be unpredictable.
The Blaze engine executes operations in the following order: deletes, updates, inserts. It does not process rows in the same order as the Update Strategy transformation receives them.
Hive targets always perform Update as Update operations. Hive targets do not support Update Else Insert or Update as Insert.
|
Weighted Average
| Supported without restrictions.
|
Updated December 13, 2018