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 Fixed Limitations

Microsoft Azure Data Lake Store Gen2 Connector Fixed Limitations

The following table describes fixed limitations:
CR
Description
CCON-19246
When you use the
Create Target
option and enable
Handle special characters
, the
Directory Override
advance target property is not honored. The target file is created in the directory specified in connection properties and the target file name includes the prefix $. Example:
$tgt_CustomerDetails.csv
CCON-19096
When you use the
Create Target
option and run a mapping to write data to an ORC target, the Secure Agent converts Timestamp data type columns to Date data type.
CCON-19014
When you use the
Create Target
option and run a mapping to write data to an ORC target, the Secure Agent converts Long data type columns to Int data type instead of Bigint data type.
CCON-18969
When you use the
Create Target
option and run a mapping to write data from a Parquet file with
OPTIONAL
field values, the
OPTIONAL
fields are created as
REQUIRED
in the target.
CCON-18928
When you use the
Create Target
option and run a mapping to write columns with LONG data type from an Avro file, the Secure Agent converts Long data type columns to Int data type instead of Bigint data type.
CCON-18898
When you use the
Create Target
option and run a mapping to write from an Avro file that contains null values, the mapping runs with the
java.lang.NullPointerException
warning.
CCON-18489
When you use the
Create Target
option and run a mapping task that reads a flat file source of size 7 GB 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.


Updated August 02, 2020