Table of Contents

Search

  1. Abstract
  2. Installation and Upgrade
  3. 10.2 HF1 Fixed Limitations and Closed Enhancements
  4. 10.2 HF1 Known Limitations
  5. 10.2 Fixed Limitations and Closed Enhancements
  6. 10.2 Known Limitations
  7. Emergency Bug Fixes Merged into 10.2
  8. Informatica Global Customer Support

Data Transformation Known Limitations (10.2)

Data Transformation Known Limitations (10.2)

The following table describes known limitations:
Bug
Description
CM-7860
When a Data Processor transformation reads Parquet input with Amazon EMR in the Hive environment, the read action might fail.
Workaround: Remove the following compression codecs from the
core-site.xml
property on all EMR instances in the clusters:
  • com.hadoop.compression.lzo.LzoCodec
  • com.hadoop.compression.lzo.LzopCodec
Add the following values:
  • org.apache.hadoop.io.compress.GzipCodec
  • org.apache.hadoop.io.compress.DefaultCodec
  • org.apache.hadoop.io.compress.BZip2Codec
  • org.apache.hadoop.io.compress.SnappyCodec
In addition, remove the
io.compression.codecs
property.
CM-7833
When using UTF-8 encoding and non-English characters in field names while importing a JSON schema, some fields with non-English characters might not be mapped.
Workaround: Provide a schema and data with UTF-8 encoding.
Cm-7830
A hierarchical to relational Data Processor transformation is set to accumulation mode with the following
Output Control
settings:
Binary output port collection
> Collect input rows to a single output set
. For a JSON to hierarchical transformation, if you change the output port to binary, the output will be multiple JSON data sets, with each set on a separate line.
CM-7823
The Data Processor transformation can show 100,002 markings by default in the Data Viewer.
Workaround: To show all markings, create the environment variable
IFCM_MAX_MARKINGS
and set it equal to
TRUE
.
B2BT-312
Service parameters are not supported for a Data Processor transformation with relational input.
Workaround: Create two Data Processor transformations. Configure the first Data Processor transformation to use Input Mapping mode without the service. Configure the second Data Processor transformation with the service and define the service parameters. Link the output of the first transformation to the second transformation. Pass the service parameters with passthrough ports through the first transformation.


Updated June 29, 2020