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 Data Lake Store Gen2 Connector Known Limitations

Microsoft Azure Data Lake Store Gen2 Connector Known Limitations

The following table describes known limitations:
CR
Description
IF-27327
When you use the
Create Target
option to create an Avro target file and add time stamp special characters in the object name, the mapping fails.
CCON-19940
When you run a mapping to read a
.ppt
or a
.mp3
source file and select
None
format type under
Formatting Options
to read data in the binary format, the data is not written to the target file as expected.
CCON-19708
When you use the
Create Target
option to create an ORC target file that uses snappy compression and run the mapping on a Linux agent, unicode characters in the data are not written as expected in the target file.
CCON-19370
When you create a mapping to read a compressed file, data preview shows junk characters.
CCON-19094
When you run a mapping to read data of Timestamp and Date data types from an ORC file, the Secure Agent truncates the data written to the target.
CCON-18967
When you use the
Create Target
option and run a mapping to write columns with INT64 data type from a Parquet file, the INT64 columns are written as INT32 instead of Bigint.
CCON-18870
When you use the
Create Target
option and run a mapping task that reads a complex file source with size 50KB or more, the mapping task fails.
Workaround: set the JVM options for type Tomcat JRE to increase the -Xms and -Xmx values in the system configuration details of the Secure Agent to avoid java heap space error. You must then restart the Secure Agent.
CCON-18710
When you use the
Create Target
option and run a mapping to write data from a Microsoft Azure Data Lake Store Gen2 flat file that contains only a header, the mapping runs successfully. However, the header is not written to the target file.
CCON-18308
Tasks fail when an authenticated proxy is configured on the Secure Agent.
CCON-15473
When a Microsoft Azure Data Lake Store Gen2 source or a target object contains special characters in headers or in the file data, the data is not written correctly to the target object, though the mapping runs successfully.


Updated August 02, 2020