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
CCON-19246
If you use
Create Target
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-19112
When you run a mapping to write data to an ORC target using the
Create Target
option, the Secure Agent converts data in Bigint data type columns to null values.
CCON-19096
When you run a mapping to write data to an ORC target using the
Create Target
option, the Secure Agent converts the columns of the Timestamp data type to Date data type.
CCON-19094
When you run a mapping to read data of Timestamp data type from an ORC file, the Secure Agent truncates the data written to the target.
CCON-19017
If you use
Create Target
and specify the object name with different extension,
Format Type
under
Formatting Options
is not honored. For example, if you select
Parquet
format type and specify
customer.avro
in the object name in the
Target Object
dialog box, the Secure Agent ignores Parquet and creates an Avro target file.
CCON-19014
When you run a mapping to write data to an ORC target using the
Create Target
option, the Secure Agent converts the columns of the Long data type to Int instead Bigint data type.
CCON-18969
When you use
Create Target
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-18967
When you use
Create Target
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-18928
When you use
Create Target
and run a mapping to write columns with LONG data type from an Avro file, the LONG columns are written as Int instead of Bigint.
CCON-18898
When you use
Create Target
and run a mapping to write from an Avro file that contains null values, the mapping runs with the
java.lang.NullPointerException
warning.
CCON-18870
When you use
Create Target
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
Create Target
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-18489
When you use
Create Target
and run a mapping task that reads a flat file source with size 7GB 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-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 from the source object to the target object, though the mapping runs successfully.


Updated August 02, 2020