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 Storage Gen2 Connector Known Limitations

Microsoft Azure Data Lake Storage Gen2 Connector Known Limitations

The following table describes known limitations:
CR
Description
CCON-23489
When you run a mapping to read a JSON file from a Microsoft Azure Data Lake Storage Gen2 source and write to a Microsoft Azure Data Lake Storage Gen2 target, the Secure Agent writes the values of double data type to the target, in exponential format.
CCON-23462
When you run a mapping to read a JSON file from a Microsoft Azure Data Lake Storage Gen2 source and write to a Microsoft Azure Data Lake Storage Gen2 target and provide an empty JSON file at runtime, the mapping runs in an infinite loop and the session log displays the following error:
java.lang.Exception: [MPSVCCMN_10094] The Mapping Service Module failed to run the job with ID [3f8bc4AAEeqRd-flz0dfjw] because of the following error: [EdtmExec_00007] [SDK_APP_COM_20000] error [JSON parsing issue:null]
CCON-22600
When you run concurrent
elastic mappings
to read from a Microsoft Azure SQL Data Warehouse source and write to a Microsoft Azure Data Lake Storage Gen2 target, some tasks fail with an internal error.
CCON-22597
When you run an
elastic mapping
to read Parquet files of size more than 20 GB from a Microsoft Azure Data Lake Storage Gen2 source and write to a Microsoft Azure SQL Data Warehouse target, the mapping fails with the following error:
org.apache.hadoop.fs.FileAlreadyExistsException
CCON-22596
When you run an
elastic mapping
to read large or moderate volume of data from a source and write to a Microsoft Azure Data Lake Storage Gen2 target in JSON format, the mapping either takes a long time to execute or fails with a timeout error.
CCON-22510
When you run an
elastic mapping
to write a parquet file to a Microsoft Azure Data Lake Storage Gen2 target, the Secure Agent fails to read decimal data.
CCON-22507
When you run an Avro to Avro or Parquet to Parquet elastic mapping with FileName field, the Secure Agent creates multiple partition files for every unique row and the mapping fails with an out-of-memory error.
CCON-22470
When you run an elastic mapping to read data from a source with FileName field and write to a Microsoft Azure Data Lake Storage Gen2 target in JSON format, the mapping fails.
Workaround: Remove the FileName field from the imported source object and run the mapping.
CCON-22344
You cannot use Microsoft Azure Data Lake Storage Gen2 Connector to read or write hierarchical data types. If you import a complex file with hierarchical data types, the mapping becomes invalid.
CCON-21942
When you run a mass ingestion task to read multiple, large files from a Microsoft Azure Data Lake Storage Gen2 source, the task might fail with a timeout error.
Workaround: To avoid timeout error, configure one of the following options:
  • Reduce the batch size in the source properties to reduce the number of threads.
  • Increase the block size and reduce the heap size to limit the number of concurrent requests.
CCON-21654
You cannot read or write compressed JSON files in an elastic mapping.
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-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-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