Table of Contents

Search

  1. Preface
  2. Part 1: Version 10.5.4 - 10.5.4.x
  3. Part 2: Version 10.5.3 - 10.5.3.x
  4. Part 3: Version 10.5.2 - 10.5.2.1.x
  5. Part 4: Version 10.5.1 - 10.5.1.1
  6. Part 5: Versions 10.5 - 10.5.0.1
  7. Part 6: Versions 10.4.1 - 10.4.1.3
  8. Part 7: Versions 10.4 - 10.4.0.2
  9. Part 8: Versions 10.2.2 - 10.2.2 HotFix 1
  10. Part 9: Version 10.2.1
  11. Part 10: Version 10.2 - 10.2 HotFix 2

What's New and Changed (10.5.4.0.1)

What's New and Changed (10.5.4.0.1)

MetaDex enhancements

MetaDex enhancements

Effective in version 10.5.3, MetaDex scanners include the following enhancements:

Informatica Intelligent Cloud Services scanner enhances MDM SaaS

Effective in version 10.5.3, the Informatica Intelligent Cloud Services MetaDex scanner can connect to MDM SaaS through REST API, fetch the resource hierarchy and the relationship data, and write the data to the output model.

MetaDex scanner jobs generate control lineage links

Effective in version 10.5.3, MetaDex scanner jobs generate control lineage links in the Catalog. You can show or hide the links on the system lineage diagrams.

Databricks Notebooks MetaDex scanner enhancements

Effective in version10.5.3, the Databricks Notebooks MetaDex scanner includes the following enhancements:
  • Include your own messages in the application log using the Logging Python module.
  • Join one or more components of the path using the join() function in os.path Python module.
  • Generate secure hash and message digest algorithms using the hashlib Python module.

Microsoft SQL Server Integration Services MetaDex scanner processes regular functions as root objects

Effective in version 10.5.3, you can use regular functions as root objects in Microsoft SQL Server Integration Services MetaDex scanner jobs.

Informatica Intelligent Cloud Services

Effective in version 10.5.3, you can scan an Informatica Intelligent Cloud Services resource through a proxy connection.

ETL scanners use information about files that match a pattern

Effective in version 10.5.3, if you have incomplete lineage in Amazon S3 or Azure Data Lake Storage file systems that is caused by wildcard characters, you can configure the Databricks Notebooks and Microsoft Azure Data Factory MetaDex scanners to access information about the file names and directory paths that include wildcards to resolve them.
For more information, see the following How-to library article:
Configure ETL scanners to use information about files that match a pattern

0 COMMENTS

We’d like to hear from you!