Table of Contents

Search

  1. Preface
  2. Introduction to Informatica Big Data Management
  3. Connections
  4. Mappings in the Hadoop Environment
  5. Mapping Objects in the Hadoop Environment
  6. Processing Hierarchical Data on the Spark Engine
  7. Stateful Computing on the Spark Engine
  8. Monitoring Mappings in the Hadoop Environment
  9. Mappings in the Native Environment
  10. Profiles
  11. Native Environment Optimization
  12. Data Type Reference
  13. Complex File Data Object Properties
  14. Function Reference
  15. Parameter Reference

Transformation Support on the Blaze Engine

Transformation Support on the Blaze Engine

Some restrictions and guidelines apply to processing transformations on the Blaze engine.
The following table describes rules and guidelines for processing transformations on the Blaze engine:
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:
  • The transformation contains stateful variable ports.
  • The transformation contains unsupported functions in an expression.
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:
  • The transformation is configured for repeatable expression masking.
  • The transformation is configured for unique repeatable substitution masking.
Data Processor
Mapping validation fails in the following situations.
  • The transformation
    Data processor mode
    is set to
    Input Mapping
    or
    Service and Input Mapping
    .
Decision
Supported without restrictions.
Expression
Mapping validation fails in the following situations:
  • The transformation contains stateful variable ports.
  • The transformation contains unsupported functions in an expression.
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:
  1. Copy external .jar files to the Informatica installation directory in the Data Integration Service machine at the following location:
    <Informatic installation directory>/services/shared/jars
    . Then recycle the Data Integration Service.
  2. On the machine that hosts the Developer tool where you develop and run the mapping that contains the Java transformation:
    1. Copy external .jar files to a directory on the local machine.
    2. Edit the Java transformation to include an import statement pointing to the local .jar files.
    3. Update the classpath in the Java transformation.
    4. Compile the transformation.
Joiner
Mapping validation fails in the following situations:
  • The transformation contains an inequality join and map-side join is disabled.
  • The Joiner transformation expression references an unconnected Lookup transformation.
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:
  • The cache is configured to be shared, named, persistent, dynamic, or uncached. The cache must be a static cache.
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:
  • The mapping specifies an identity match type.
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:
  • The reset property for the transformation is enabled.
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:
  • The Sorter transformation is connected directly to flat file targets.
  • The target is configured to maintain row order.
  • The sort key is not a binary data type.
If any of the conditions are not true, the Blaze engine performs a local sort.
Mapping validation fails in the following situations:
  • The target is configured to maintain row order and the Sorter transformation is not connected directly to a flat file target.
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 Update Strategy transformation is connected to more than one target.
  • The Update Strategy transformation is not located immediately before the target.
  • The Update Strategy target is not a Hive target.
  • The Update Strategy transformation target is an external ACID table.
  • The target does not contain a primary key.
  • The Hive target property to truncate the target table at run time is enabled.
  • The Hive target property to create or replace the target table at run time is enabled.
The mapping fails in the following situation:
  • The target is not ORC bucketed.
  • The Hive target is modified to have fewer rows than the actual table.
Compile validation errors occur and the mapping execution stops in the following situations:
  • The Hive version is earlier than 0.14.
  • The target table is not enabled for transactions.
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:
hive.support.concurrency true hive.enforce.bucketing true hive.exec.dynamic.partition.mode nonstrict hive.txn.manager org.apache.hadoop.hive.ql.lockmgr.DbTxnManager hive.compactor.initiator.on true hive.compactor.worker.threads 1
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 November 09, 2018