Table of Contents

Search

  1. Abstract
  2. PowerExchange for Amazon Redshift
  3. PowerExchange for Amazon S3
  4. PowerExchange for Cassandra
  5. PowerExchange for Cassandra JDBC
  6. PowerExchange for DataSift
  7. PowerExchange for Facebook
  8. PowerExchange for Google Analytics
  9. PowerExchange for Google BigQuery
  10. PowerExchange for Google Cloud Storage
  11. PowerExchange for Greenplum
  12. PowerExchange for HBase
  13. PowerExchange for HDFS
  14. PowerExchange for Hive
  15. PowerExchange for JD Edwards EnterpriseOne
  16. PowerExchange for LDAP
  17. PowerExchange for LinkedIn
  18. PowerExchange for MapR-DB
  19. PowerExchange for Microsoft Azure Blob Storage
  20. PowerExchange for Microsoft Azure Cosmos DB SQL API
  21. PowerExchange for Microsoft Azure Data Lake Store
  22. PowerExchange for Microsoft Azure SQL Data Warehouse
  23. PowerExchange for Microsoft Dynamics CRM
  24. PowerExchange for MongoDB
  25. PowerExchange for Netezza
  26. PowerExchange for Salesforce
  27. PowerExchange for SAP NetWeaver
  28. PowerExchange for Snowflake
  29. PowerExchange for Tableau
  30. PowerExchange for Teradata Parallel Transporter API
  31. PowerExchange for Twitter
  32. PowerExchange for Web Content-Kapow Katalyst
  33. Informatica Global Customer Support

PowerExchange Adapters for Informatica Release Notes

PowerExchange Adapters for Informatica Release Notes

PowerExchange for Microsoft Azure Blob Storage Known Limitations (10.2.2)

PowerExchange for Microsoft Azure Blob Storage Known Limitations (10.2.2)

The following table describes known limitations:
Bug
Description
OCON-18196
When you create a dynamic mapping to read multiple files from a directory and override the directory, the mapping fails with the following error:
java.lang.Exception: [MPSVCCMN_10094] The Mapping Service Module failed to run the job with ID [-Xa1lQmeEemYfoedBRvJBg] because of the following error: [EdtmExec_00007] java.lang.RuntimeException: org.apache.avro.AvroTypeException: Found Avro_Mappingflow, expecting Avro_dynamic_source, missing required field c_acctbal
Workaround: Verify that the override directory contains a source file with the same name as the imported object and rerun the dynamic mapping.
OCON-17842
When you use the
Create Target
option to create a Microsoft Azure Blob Storage target and select Flat as the Resource Format, fields are not getting propagated to the target.
Workaround: Enable column projection and create fields manually in the target file and run the mapping.
OCON-17642
When you enable Mapping Flow in a mapping that reads data from a flat file source and writes to a flat file target, the mapping fails with the following error in the native environment:
java.lang.Exception: [MPSVCCMN_10094] The Mapping Service Module failed to run the job with ID [Ic2j9ASPEemTlSYmtVHPww] because of the following error: [EdtmExec_00007] Exception: /tmp/insertd29a7def_bb59_452d_8051_ea4b4630807b9132318161205585091.azb (No such file or directory)
Workaround: Remove the FileName field from the imported source object and rerun the mapping.
OCON-15930
When you create a Microsoft Azure Blob Storage data object, the value of the folder path is displayed incorrectly in the
Resources
tab.
OCON-12420
When you read or write a blob that has special characters, the mapping fails on the Spark engine.
OCON-12417
For the write operation, when you run a mapping on the Spark engine and the folder path contains special characters, the Data Integration Service creates a new folder.
OCON-12352
When a JSON file contains special characters, the Data Integration Service does not read the data correctly in the Spark mode.
OCON-12327
The write operation fails for a flat file in the native environment when single or double quotes are selected as text qualifier.
OCON-12318
The Data Integration Service adds an extra blank new line at the end when you read or write a flat file in the native environment or in the Spark mode.
OCON-10125
When you read data from or write data to Microsoft Azure Blob Storage, the entire blob gets downloaded in the staging directory even if you cancel the mapping.