Table of Contents

Search

  1. Abstract
  2. 2020 - August
  3. 2020 - July
  4. 2020 - April
  5. 2020 - February
  6. 2020 - January
  7. 2019 - November
  8. 2019 - September
  9. 2019 - August
  10. 2019 - July
  11. 2019 - June
  12. 2019 - May
  13. 2019 - April
  14. 2019 - March
  15. Informatica Global Customer Support

Connector Release Notes

Connector Release Notes

Microsoft Azure BLOB Storage V3 Known Limitations

Microsoft Azure BLOB Storage V3 Known Limitations

The following table describes known limitations:
CR
Description
IF-12413
When you edit metadata in the
Fields
tab in a mapping, all native data types change to Bigint and you cannot change the scale and precision of data types except string.
ICS-9832
When you select Create Target in a mapping and configure the formatting options, the Secure Agent ignores the specified formatting options.
CCON-15075
When you configure a proxy server through Informatica Cloud Secure Agent user interface, the session log does not log the proxy server details.
Workaround: Configure the proxy server by setting the JVMOptions for your secure agent in the Administrator service.
CCON-15053
When you read data from a directory source and configure the Blob Container Override in the source advanced properties, the tasks read data from the container configured in the connection properties and ignore the Blob Container Override in the source advanced properties.
CCON-14123
Data Preview does not work when you read or write a compressed file.
CCON-14117
When you write a file to a target, the data gets truncated if the source file has values containing more than 4000 characters even after increasing the precision of the data type. This might result into data loss.
CCON-12636
When you write a JSON file of size 1GB or more, the task fails with the java heap space error.
Workaround: Set the JVM options for type DTM to increase the -Xms and -Xmx values in the system configuration details of the Secure Agent.
CCON-12616
When you write a JSON file in which column names include unicode characters, the task fails.
CCON-12612
When you write an Avro or a Parquet file that contains null values, the mapping task writes incorrect data in the target for the fields having null values.
CCON-12300
When you use Create Target to write an Avro file, the schema is created with primitive data types without providing an option to allow null values.
Workaround: Manually edit the schema to allow null values as required. For example:
{"type":"record","name":"S3_Avro_CT_N","fields":[
{ "name":"c_custkey" , "type":["int","null"]},
{ "name":"c_name" , "type":"string"}
{ "name":"c_nationkey" , "type":["long","null"]}
]}
CCON-11979
Microsoft Azure Blob Storage V3 Connector displays the following common error message for all failed mappings:
The Integration Service found Informatica Hadoop distribution directory [/data/home/cloudqa/staging1/apps/Data_Integration_Server/52.0.16/ICS/main/distros/cloudera_cdh5u8/lib and /conf] for Hadoop class loader.


Updated August 02, 2020