Table of Contents

Search

  1. Preface
  2. Dropped Support
  3. Installation and Upgrade
  4. 10.5.6 Fixed Issues
  5. 10.5.6 Known Issues
  6. Emergency Bug Fixes Merged into 10.5.6
  7. Cumulative Known Limitations
  8. Informatica Global Customer Support

Release Notes (10.5.6)

Release Notes (10.5.6)

Enterprise Data Catalog Known Issues (10.5.6)

Enterprise Data Catalog Known Issues (10.5.6)

The following table describes known issues that were found in 10.5.6:
Issue
Description
EIC-67483
Export of lineage and impact analysis of the asset summary to a Microsoft Excel file leads to noticeable delays
EIC-67474
Resources sometimes fail to access and publish metadata at run time.
EIC-67442
JSONL metadata extraction fails with OutOfMemoryError for file sizes that exceeds more than 2 MB.
EIC-67440
The metadata extraction of the Amazon S3 V2 resource incorrectly displays the column information in the multi-level hierarchical XML files.
EIC-67422
After the Tika 2.9.2 upgrade, the system incorrectly excludes compressed files with certain Word, Excel, or PowerPoint extensions from profiling.
EIC-67297
JSON keys with the array keyword show empty profiling results and data domains.
EIC-67193
Hive-style partitioned CSV files with different delimiters for each partition display incorrect profiling results.
EIC-67166
When you extract XML files in Amazon S3 or Azure Data Lake Storage Generation 2 (V2) resources, elements appear as String rather than the correct data types.
EIC-67048
When you disable partition pruning option, non-hive style partition parquet profiling fails.
EIC-66841
Amazon S3 and Azure Data Lake Storage Gen2 fail to send unstructured files in hive-style Avro and parquet partition folders for profiling.
EIC-66681
EIC-66682
Schema merge fails in the following scenarios when:
  • A schema drift occurs.
  • The root elements differ.
  • The data types of the fields differ.
EIC-66428
EIC-66423
The Enrichment Migration Utility fails to migrate enrichments for objects that has the same name and the same parent.
Workaround: Import the enrichments for these objects manually.

0 COMMENTS

We’d like to hear from you!