Clients Scenario: I have an entity with custom data format. This entity is associated with an EDQ action of a post ingestion WF. While executing the action, I got the exception "Entity with data file CUSTOM is not supported by EDQ"
As an administrator of new data platform, I want the ability to easily on-board AD users or have a strategy to expose data catalog with limited functionality to new users, so that the users to explore the data catalog and request for more access
Customer expects a ZDP API that would allow them to download files from the Data Lake without having to communicate with the storage layer directly. The data may be stored in HDFS, S3, ADLS or GCP. Basically current we can export records in a file...
Today if the customer has to sync the metadata from Hcatalog/Hive, they have run hive inventory action (which is sub-optimal in performance) per schema. Request is to be able to automatically scan hcatalog and catalog the changes/new tables.