Creating a custom entity to represent Fabric Lakehouse table

Yeshan Santhush Indiketiya Hewage 0 Reputation points
2024-06-06T05:51:03.0933333+00:00

Since Purview scan doesnt support the scanning of Fabric Lakehouse tables, I tried creating a custom type using the Purview REST API. However I'm struggling to set up columns within the custom entity (which uses the custom type i have created). Can anyone suggest on how to set up columns to the entity.

Microsoft Purview
Microsoft Purview
A Microsoft data governance service that helps manage and govern on-premises, multicloud, and software-as-a-service data. Previously known as Azure Purview.
1,026 questions
{count} votes

2 answers

Sort by: Most helpful
  1. PRADEEPCHEEKATLA-MSFT 84,051 Reputation points Microsoft Employee
    2024-06-06T08:36:15.1433333+00:00

    @Yeshan Santhush Indiketiya Hewage - Thanks for the question and using MS Q&A platform.

    It seems like you are trying to create a custom entity to represent Fabric Lakehouse table in Microsoft Purview. While Purview scan doesn't support the scanning of Fabric Lakehouse tables.

    According to the official documentation: How to get lineage from Microsoft Fabric items into Microsoft Purview

    Currently for all Fabric items besides Power BI, only item level metadata and lineage will be scanned. Scanning metadata and lineage of sub level items like Lakehouse tables or files isn't yet supported.

    You can create a custom type using the Purview REST API.

    To set up columns within the custom entity, you can use the following steps:

    1. First, create a custom type using the Purview REST API. You can use the following API endpoint to create a custom type:
         POST https://account-name.catalog.purview.azure.com/api/atlas/v2/types
      
      In the request body, you can specify the name and description of the custom type. For example:
         { 
         "name": "MyCustomType", 
         "description": "Custom type for Fabric Lakehouse table" 
         }
      
    2. Once you have created the custom type, you can create a custom entity using the following API endpoint:
         POST https://account-name.catalog.purview.azure.com/api/atlas/v2/entity/bulk 
      
      In the request body, you can specify the details of the custom entity, including the name, description, and type of the entity. For example:
         { "entities": [ { "typeName": "MyCustomType", "attributes": { "qualifiedName": "mycustomentity@account-name", "name": "MyCustomEntity", "description": "Custom entity for Fabric Lakehouse table" } } ] }
      
    3. To add columns to the custom entity, you can use the following API endpoint:
         POST https://account-name.catalog.purview.azure.com//api/atlas/v2/entity/entity-guid/attributes
      
      In the request body, you can specify the details of the column, including the name, description, and data type. For example:
         { "typeName": "string", "values": [ "Column1" ], "name": "Column1", "description": "Column 1 of Fabric Lakehouse table" }
      
      You can repeat this step to add more columns to the custom entity.

    For more details, refer to How to create custom entity in Azure purview?.

    Hope this helps. Do let us know if you any further queries.


    If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.


  2. PRADEEPCHEEKATLA-MSFT 84,051 Reputation points Microsoft Employee
    2024-06-13T05:17:49.4666667+00:00

    @Yeshan Santhush Indiketiya Hewage - I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to accept the answer .

    Ask: Creating a custom entity to represent Fabric Lakehouse table

    Solution: The issue is resolved. I managed to solve it by creating columns separately as different entities in bulk, and then create the custom entity representing the Lakehouse while linking the column entities' guids to it.

    If I missed anything please let me know and I'd be happy to add it to my answer, or feel free to comment below with any additional information.

    If you have any other questions, please let me know. Thank you again for your time and patience throughout this issue.


    Please don’t forget to Accept Answer and Yes for "was this answer helpful" wherever the information provided helps you, this can be beneficial to other community members.

    0 comments No comments