Table of Contents


  1. Abstract
  2. Informatica Installation
  3. Informatica Upgrade
  4. 10.1 Fixed Limitations and Closed Enhancements
  5. 10.1 Known Limitations
  6. Informatica Global Customer Support

Transformation Known Limitations

The following table describes known limitations:
The Hierarchical to Relational transformation does not support Avro and Parquet input formats.
The Match transformation performs identity analysis on the key field port and ignores the match strategy ports when you do not include the key field port in the match strategy. The transformation does not perform match analysis correctly on the key field data and does not create accurate clusters.
You cannot copy fields to the Ports view of a REST Web Service Consumer transformation.
Workaround: Manually add the ports to the REST Web Service Consumer transformation.
If you do not define the input schema or map the request input group element to the root element of REST consumer input, REST fails without displaying an error message.
When adding custom ports, non-reusable REST transformation incorrectly appends new custom ports to deleted custom ports.
Workaround: Re-create the transformation.
When you use the ABORT() function in an Expression transformation, the Data Integration Service does not process the Expression transformation.
Workaround: Change the default value of the output port to 0 and run the mapping again.
When the Data Integration Service performs a cached lookup and an uncached lookup on Microsoft SQL Server Uniqueidentifier data types, it does not return the same number of rows.
The Key Generator transformation cannot generate unique sequence ID values in a Hadoop environment.
If you use the transformation wizard to create a Hierarchical to Relational transformation or Relational to Hierarchical transformation in one folder, and try to reference a schema in another folder, the wizard might fail.