Creating technical lineage via Edge (beta)

This topic provides an overview of the necessary steps to create a technical lineage for the JDBC data sources and ETL tools or a custom technical lineage on Edge.

To view the steps to create technical lineage for your data source, select the data source and connection type, if applicable. For a listed of supported data sources and their corresponding connection types, go to Supported data sources for technical lineage.

Tip 

Select a data source and the connection type if needed to see the related information.

Currently, you see the information for:

X

Before you begin

Requirements and permissions

  • A global role with the following global permissions:
    • Data Stewardship Manager
    • Manage all resources
    • System administration
    • Technical lineage
  • A resource role with the following resource permission on the community level in which you created the BI Data Catalog domain:
    • Asset: add
    • Attribute: add
    • Domain: add
    • Attachment: add
  • Necessary permissions to all database objects that technical lineage via Edge accesses.
  • Permissions required for the data source that you selected:
    You need read access on the SYS schema.
    You need read access on the SYS schema and the View Definition Permission in your SQL Server.
    You need read access on information_schema:
    • bigquery.jobs.create
    • bigquery.readsessions.create
    • bigquery.tables.getData
    • bigquery.readsessions.getData
    GRANT SELECT, at table level. Grant this to every table for which you want to create a technical lineage.
    The role of the user must be the owner of the views in PostgreSQL, and the username of the user must be specified in the JDBC connection that you use to access PostgreSQL.
    You need read access on information_schema. Only views that you own are processed.
    SELECT, at table level. Grant this to every table for which you want to create a technical lineage.
    A role with the LOGIN option.
    SELECT WITH GRANT OPTION, at Table level.
    CONNECT ON DATABASE
    Note The following permissions are the same, regardless of the ingestion mode: SQL or SQL-API.

    You need a role that can access the Snowflake shared read-only database. To access the shared database, the account administrator must grant the IMPORTED PRIVILEGES privilege on the shared database to the user. The username of the user must be specified in the JDBC connection that you use to access Snowflake.

    Tip If the default role in Snowflake does not have the IMPORTED PRIVILEGES privilege, you can click the Add property button to add a custom parameter with the following values specified:
    FieldValue
    NamecustomConnectionProperties
    TypeText
    Encryption

    Select one of the following encryption methods: 

    • Not encrypted (plain text)
    • Encrypted with public key
    • To be encrypted by Edge management server
    Valuerole=METADATA
    You need read access on the DBC.
    You need read access to the following dictionary views:
    • all_tab_cols
    • all_col_comments
    • all_objects
    • ALL_DB_LINKS
    • all_mviews
    • all_source
    • all_synonyms
    • all_views
    You need read access on definition_schema.
    • Your user role must have privileges to export assets.
    • You must have read permission on all assets that you want to export.
    • You have added the Matillion certificate to a Java truststore.
    • You have at least a Matillion Enterprise license.

Steps

  1. Enable and configure technical lineage via Edge.
  2. Create an Informatica Intelligent Cloud Services connection.

    Note Collibra Data Intelligence Cloud 2023.03 or newer is required to use the Informatica Intelligent Cloud Services (IICS) connection.

  3. Create a Matillion connection.

    Note Collibra Data Intelligence Cloud 2023.03 or newer is required to use the Matillion connection.

  4. Create a Shared Storage connection.
  5. Prepare the data source files and store the data source files in the folder that you create when you create the Shared Storage connection in the previous step.
  6. Create a custom technical lineage JSON file and store the JSON file in the folder that you create when you create the Shared Storage connection in the previous step.
  7. Add a technical lineage capability to an Edge site.

What's next?

View the technical lineage.