The July 2024 release of Metadata Command Center includes the following changed behaviors.
Custom delimiter behavior in delimited files
If you add a custom delimiter, you override the default list of delimiters. When you specify a delimiter, characters from the default list are not considered as delimiters.
Previously, a custom delimiter that you specify was appended to the default list of delimiters.
You can specify custom delimiters when you configure the following catalog sources:
•Amazon S3
•File System
•Google Cloud Storage
•Hadoop Distributed File System
•Microsoft Azure Blob Storage
•Microsoft Azure Data Lake Storage Gen2
•Microsoft Fabric OneLake
•Microsoft OneDrive
•Microsoft Sharepoint
•Oracle Cloud Storage
•SFTP File System
For more information about configuring a custom delimiter for catalog sources, see Catalog Source Configuration.
Access and name change of Connection Assignment
The Connection Assignment page is now named Assign Connections and you can access it from the Lineage tab on the Configure page.
Previously, the page was named Connection Assignment, and you could access it from the Monitor page.
For information about assigning connections, see Connections.
Run profiles on hierarchical fields
You can run profiles on hierarchical fields even if you extract group elements using the Extract Group Elements from Hierarchical Files property for the following catalog sources:
•Amazon S3
•Google Cloud Storage
•Microsoft Azure Data Lake Storage Gen2
Previously, you could not run profiles on hierarchical fields if you extract group elements for these catalog sources.
If you delete a catalog source in Metadata Command Center and the deletion job fails, you might still see partial or complete scan results in Data Governance and Catalog. Such catalog sources continue to appear in the list of catalog sources in Metadata Command Center but are marked as Deleted. The only action you can take is to delete them again. Once fully deleted with all associated assets deleted from Data Governance and Catalog, the catalog source doesn't appear in the list.
Previously, if a deletion job failed, the catalog source was removed from Metadata Command Center, but its associated assets still appeared in Data Governance and Catalog.